implement

Files (4)

• SKILL.md
• batch-git-operations.md · references/
• error-handling.md · references/
• verification.md · references/

SKILL.md (first lines)

# Implement — Execute an Issue

Take a validated issue from the pipeline and implement it.

## Process

### 0. Confirm

Read the issue body, acceptance criteria, and any related spec. Present a summary to the user and wait for confirmation before proceeding.

### 1. Set up workspace

Use the `worktree` skill to create an isolated branch:
```bash
git worktree add ../<project>-<feature> -b feat/<feature>
cd ../<project>-<feature>
```

### 2. Execute tasks

Work through each task continuously:

- Implement one task at a time — follow the acceptance criteria, write minimal code
- Run the project's test suite after each task (e.g., `go test`, `vitest`, `pytest`)
- Fix any failures before continuing
- Mark tasks complete with `[x]` as you go

**Keep it minimal.** Implement the criteria, nothing more. No speculative features.

**Follow conventions.** Read neighboring files, check package manifests, reuse existing utilities. Do not introduce new dependencies without checking first.

### 3. Self-review

After all tasks are done, run a quick self-review (see [verification.md](references/verification.md)):

- Cross-check each acceptance criterion against the implemented code
- Scan for speculative code outside the issue scope
- Verify commit messages follow conventional commit format

### 4. Commit

```bash
git add -A
git commit -m "feat: <summary of what was implemented>"
```

## When to Stop

Stop execution and ask the user when:
- A test failure persists after 3 fix attempts
- You need clarification (ambiguous AC, missing context, conflicting requirements)
- A dependency is missing or cannot be resolved

See [error-handling.md](references/error-handling.md) for the full retry and escalation strategy.

## Next Steps

After committing, suggest the next step:
- **`code-review`** — formal review of the implementation
- **`context-sync`** — if new domain terms or conventions emerged

## Tips

- The `tdd` skill is available for stricter test-first discipline — load it if the project uses a test framework and you want red-green-refactor cycles
- Convention rules live in the project's `CONTEXT.md`, not in this skill — read it when working in an unfamiliar codebase
- For bulk file renames/reorganizations across a repo, see [batch-git-operations.md](references/batch-git-operations.md) — use `execute_code` with Python, not shell loops

From atalariq/skills, MIT.

More from atalariq/skills