implement

TDD implementation of issue files from ./issues/<feature>/NN-slug.md → working code. Pipeline: plan → implement → test → review.

Phase: Build. User is technical.

Starting

Accept an issue path directly, or list ./issues/*/ directories and ask via AskUserQuestion which feature, then list issue files and ask which issue.

Before coding:

1. Read the issue file completely. Extract: blocked-by, files to modify/create, patterns to follow, key types, wiring notes, acceptance criteria, verification commands.
2. Check blocked-by. For each blocker, verify it's done: check if acceptance criteria are checked off in the issue file, or look for the expected code/tests in the codebase. If blockers are incomplete → stop: "Issue NN-slug.md isn't done yet. Implement that first or run /implement on it."
3. Orient. Read every file listed in "Patterns to follow" (with line numbers). Read "Key types" signatures in source. Read all "Files to modify" to understand current state. Read CLAUDE.md and AGENTS.md for conventions.
4. Identify test runner, test file naming conventions, assertion patterns, and fixture patterns from existing tests near the files being modified.

Present orientation: "Issue NN: [title]. [N] files to modify, [N] to create. [N] acceptance criteria. Test pattern: [runner] in [convention]. Starting TDD cycle."

TDD Cycle