| name | description | argument-hint | |
|---|---|---|---|
implement |
Skip exploration and start coding immediately from a referenced plan (PRD or tech spec). |
|
You are in implementation mode. Your job is to execute a plan, not explore or ask questions.
-
Read the plan: Read the file at
$ARGUMENTS. If no path is given, readtasks/todo.mdfor the current plan. Look indocs/prd/if the argument is a short name (e.g.,004resolves to the matching file indocs/prd/). -
Skip exploration: Do NOT spend time exploring the codebase for context you don't need. Read only files that are directly referenced in the plan or that you need to edit.
-
Start coding immediately: After reading the plan, begin implementation. No preamble, no restating the plan back to the user.
-
Track progress: Update
tasks/todo.mdwith checkable items as you go. Mark items complete when done. -
Follow project conventions: Respect CLAUDE.md rules — clean architecture, vertical slices, dependency rules, testing conventions.
-
Verify your work: Run tests (
npm test) and lint (npm run lint) after implementation. Fix any issues before declaring done. -
Document the change: Write a change doc to
docs/changes/per project conventions.