菜单
Implement an approved technical plan from thoughts/shared/plans/. Use when executing a plan that was created with create-plan. Follows phases, updates checkboxes, and pauses for human verification between phases. Reports a structured walkthrough summary inline at the end.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | implement-plan |
| description | Implement an approved technical plan from thoughts/shared/plans/. Use when executing a plan that was created with create-plan. Follows phases, updates checkboxes, and pauses for human verification between phases. Reports a structured walkthrough summary inline at the end. |
| allowed-tools | Read, Write, Edit, Bash, Agent |
Implement an approved technical plan phase by phase.
If plan path provided: read the plan completely, check for existing checkmarks (- [x]), read all referenced files, then begin.
If no plan path: ask for one.
- [x]) in the plan as you complete sections/deep-module — it enforces interface-first design and flags shallow abstractions before they're writtenIssue in Phase [N]:
Expected: [what the plan says]
Found: [actual situation]
Why this matters: [explanation]
How should I proceed?
make check test # or project-specific verification commands
Then pause for human verification:
Phase [N] Complete - Ready for Manual Verification
Automated verification passed:
- [checks that passed]
Please perform manual verification:
- [manual items from plan]
- Run `/deep-module` to review encapsulation quality of modules added in this phase
Let me know when manual testing is complete to proceed to Phase [N+1].
Do NOT check off manual testing items until confirmed by the user. If instructed to run multiple phases consecutively, skip pauses until the last phase.
所有 phase 完成（含手動驗證確認）後，不要直接回報「done」。 改為：
~/.claude/skills/implement-plan/references/walkthrough.mdplan 變大後，口頭摘要會遺漏「與計畫差異」「未驗證風險」「後續 follow-up」等對使用者 最有價值的資訊。Walkthrough 是以穩定格式回報這些資訊的唯一機制。
If plan has existing checkmarks:
If plan already has a walkthrough file, the previous run completed fully. Check the walkthrough for any unfinished sections before continuing.
Document codebase as-is via parallel sub-agents. Use when researching how code works, mapping architecture, or answering questions about existing systems. Auto-detects thoughts/ directory — if present, integrates historical context and syncs; if absent, skips those steps.
Create the Questions artifact before codebase research, design, planning, or implementation. Use for feature tickets, architecture changes, unclear code work, CRISPY/QRSPI Questions phase, or when the agent needs to define code-answerable unknowns and human questions before researching or planning.
Create a concise Design Concept artifact after questions and codebase research are available. Use for CRISPY/QRSPI Design phase, architecture alignment, feature design discussion, or turning current-state research into a small human-reviewable proposed shape before detailed planning.
Create an interface-first Structure Outline before detailed planning or implementation. Use for CRISPY/QRSPI Structure Outline phase, vertical planning, method signatures, type contracts, API/component boundaries, or converting an accepted design concept into end-to-end slices with verification checkpoints.
Create comprehensive handoff documents for transferring work to another agent session. Use when the user requests to create a handoff, end a session, or document work-in-progress for future continuation.
Create detailed implementation plans through interactive research and iteration. Use when starting a new feature or ticket that needs a comprehensive technical plan. Saves plans to the repo-appropriate plans location and emits Personal Knowledge events when applicable.