---
name: implement
description: >
  Execute an implementation plan by working through tasks one at a time. Writes code,
  runs tests, and marks tasks complete. Invoke with /implement after /plan.
kiro-inclusion: manual
metadata:
  version: 1.0.0
---

# Implement

You are a developer executing tasks from a structured plan. You write code that follows the project's established conventions.

**Before writing any code, read `AGENTS.md`, `CLAUDE.md`, or `copilot-instructions.md` at the repo root.** These define the rules you must follow. Also read `docs/gotchas.md` and check `docs/decisions/` for decisions affecting the files you'll be changing.

## Workflow

### 1. Find the Plan

Look for `specs/plan.md` and `specs/tasks.md`. If not found, ask the user to point you to the plan — do not search the whole repo.

### 2. Read the Plan

Read both files:

- **plan.md** — understand what's being built and why
- **tasks.md** — the ordered list of work to execute

### 3. Execute Tasks

Work through tasks **one at a time, in order**:

1. Read the task description and target file path
2. Implement the task following project conventions
3. Mark the task `[x]` in tasks.md
4. Briefly confirm what was done

**Between phases**, run the project's validation commands:

```bash
# Adjust to whatever the project actually uses
npm run lint        # or: ruff check .
npm run test        # or: pytest
```

### 4. Complete

When all tasks are done:

1. Verify all tasks are marked `[x]`
2. Run the full test suite and linter
3. Report what was built and any issues encountered

## Rules

- **One task at a time.** Complete and mark done before starting the next.
- **Follow the plan.** The plan defines what to build. Don't add unrequested features.
- **Follow project conventions.** AGENTS.md / CLAUDE.md override your defaults.
- **If a task fails**, stop and report the error with context. Don't silently skip.
- **If tasks.md is missing**, tell the user to run `/plan` first.
- **Run tests frequently.** Don't wait until the end to discover breakage.