メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ai-driven-dev/framework --skill 02-implementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.
Capture durable project learnings. Use when the user wants to remember, record, or formalize a decision, convention, lesson, pitfall, reusable workflow, or review finding. Not for preferences or temporary notes.
SOC 職業分類に基づく
SKILL.md を表示中
| 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 |
Run an existing plan to write its code, one phase at a time, until every acceptance criterion holds.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | prepare | Resolve the plan, branch, mark it in-progress | a plan path |
| 02 | execute | Loop the phases, code and assert each | prepared plan |
| 03 | finalize | Verify and mark the plan implemented | coded phases |
Run them in order, 01 → 03.
Before running an action, read its file in actions/, not only the table or assets.
pending → in-progress → implemented (or blocked), and each phase through pending → in-progress → done. The in-progress values are runtime markers; only done and implemented need to land in a commit.done, plus a final commit for the plan reaching implemented. Never leave the tree dirty at a phase boundary. Do not scatter separate in-progress status commits: one context now owns both code and status, so there is nothing to guard against.references/blocked.md: the conditions that make a plan blocked and need a human.