02-implement — Claude Code skill: what it does, how to install
02-implement implements an existing plan in code, phase by phase, until every acceptance criterion passes. Useful when the plan is ready and the code is not.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-dev@aidd-frameworkWhat 02-implement does
The skill takes over where planning ends and walks a written plan one phase at a time. Three step files sit in actions/: prepare resolves the plan and the branch, execute writes and validates each task, finalize runs validation and marks the plan implemented.
Statuses move from pending to in-progress to done for phases, and reach implemented for the plan itself. The in-progress marker stays out of commits. Each validated task gets one local commit with its code, tests and docs inside; a task is never split by file or by step.
Formatting goes through the project's own formatters or hooks, so nobody edits code by hand. A task that will not pass sends the plan to blocked or back into planning. With no plan to resolve, prepare halts before a single line is written.
What it helps with
- turn a written plan into working code, phase by phase
- keep one commit per validated task, tests and docs included
- mark a phase
donein its last task commit - stop cleanly when there is no plan to resolve
- flag the plan
blockedwhen a task will not pass validation
Example prompts for the agent
- Implement the plan in
docs/plans/auth-refactor.md, phase by phase. - Continue from phase 2 of
billing.mdand commit each validated task. - Close the plan out as
implementedonce the acceptance criteria pass.
How to install 02-implement
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-dev@aidd-frameworkThis installs the whole aidd-dev plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-implement -a claude-code3Manually: put the files in place
~/.claude/skills/02-implement/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/02-implement/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-implement -a codex2Manually: put the files in place
.agents/skills/02-implement/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-implement -a cursor2Manually: put the files in place
.cursor/skills/02-implement/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-dev/skills/02-implement2Manually: put the files in place
.github/skills/02-implement/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-implement -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-dev/skills/02-implementManually: put the files in place
.devin/skills/02-implement/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-implement -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 02-implement
How do I install 02-implement in Claude Code?
Add the marketplace with /plugin marketplace add ai-driven-dev/framework, then install the plugin: /plugin install aidd-dev@aidd-framework.
What does 02-implement do?
It writes the code for a plan you already have, one phase at a time, validating every task. At the end it checks the result and closes the plan as implemented.
Do I need a plan before using it?
Yes. prepare looks for the plan first and stops when there is none. Writing plans and reviewing diffs are outside what this skill does.
Source text
SKILL.md · MIT
--- name: 02-implement description: Write an existing plan's code, phase by phase, until every acceptance criterion holds. Use when a plan exists and needs implementing. Do NOT use to write a plan, review a diff. argument-hint: plan --- # Skill: implement ```mermaid flowchart LR prepare --> execute --> finalize --> implemented prepare -->|missing plan| stop execute -->|fix, next task or phase| execute execute --> blocked execute --> replan finalize -->|validation fails| finalize finalize --> blocked finalize --> replan ``` ## Actions Run actions in order. Read each action file in `actions/` before executing it. | Action | Does | | -------- | ------------------------------------- | | prepare | resolve the plan and branch | | execute | implement and validate each task | | finalize | validate and mark the plan implemented | ## Transversal rules - Track the plan through `pending → in-progress → implemented` (or `blocked`). - Track phases through `pending → in-progress → done`. - Treat `in-progress` as a runtime marker. - Never commit `in-progress` alone. - Follow user and project commit instructions. - Push only when requested. - By default, make one local commit per validated task. - Include all its code, tests and docs together. - Group tasks only when they cannot be validated separately. - Never split a task by step or file. - Exclude unrelated changes. - Include `done` in the phase's last task commit. - Make a final commit for `implemented`. - Use project formatters or hooks. - Never format code manually.
© AI-Driven Dev · MIT · ai-driven-dev/framework