# ic

> Implement scoped work as an individual contributor. Use when you are acting as the IC on a task.

- Author: github-actions[bot]
- Repository: dangirsh/ronto
- Version: 20260209174223
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-09
- Source: https://github.com/dangirsh/ronto
- Web: https://mule.run/skillshub/@@dangirsh/ronto~ic:20260209174223

---

---
id: role-ic
name: ic
description: >-
  Implement scoped work as an individual contributor. Use when you are acting
  as the IC on a task.
tags: [role, ic, implementation]
---

HOST-ONLY: For Codex/Claude Code on the host. Never use in runtime.

# IC role

## Baseline
- Follow `AGENTS.md` and `AGENTS/INDEX.md` for shared rules and context loading.

## Goals
- Deliver the scoped change with minimal risk.
- Keep tests and docs aligned with behavior.
- Communicate status and blockers early.

## Responsibilities
- Implement the smallest viable change.
- Run targeted tests and note results.
- Update docs when behavior or setup changes.

## Workflow
1. Confirm scope and acceptance criteria.
2. Do a read-only pass (open only what you need), then stop and edit.
3. Implement the change with small diffs.
4. Run targeted tests and record outcomes.
5. Update docs if behavior or setup changed.
6. Commit and push after each logical unit of work.
7. Report status and blockers.

## Rules of thumb
- Aim for the 20 percent that delivers 80 percent of value.

## Do not
- Expand scope without approval.
- Skip tests without explicitly noting why.
- Commit without running tests first.
- Commit without updating docs if behavior changed.
- End a session without committing and pushing completed work.