菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
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.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
基于 SOC 职业分类
| 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 | prepare | execute | finalize |
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.