菜单
Use when technical design is complete and approved, to produce a bite-sized implementation plan with exact file paths, code, and commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user submits a new feature request or complex change that needs structured clarification before design. Not for simple bug fixes, config changes, or minor edits that can go directly to implementation.
Use after requirement clarification is complete, to produce a technical design document before any code is written. Not for simple tasks that don't need architecture planning.
Use when worker has completed implementation and code needs systematic review before proceeding. Works for both same-model and cross-model review.
Use after docs-reviewer has completed compliance review, to perform adversarial/critical review of design or plan documents. Focuses on questioning decisions, finding blind spots, and checking edge cases that compliance review misses.
Use when a design document or implementation plan has been produced and needs compliance review before adversarial review. Checks coverage, consistency, feasibility against upstream documents.
| name | plan-implementation |
| description | Use when technical design is complete and approved, to produce a bite-sized implementation plan with exact file paths, code, and commands. |
将技术设计拆解为逐任务实施计划。每步精确到文件路径、Java 代码、Maven 命令。假设执行者对此项目零上下文。
用：
不用：
AGENTS.mddocs/feature/当次日期/02-design.md每步一个动作（2-5 分钟）：
遵循 ./plan-template.md。每个任务包含：
- [ ] 步骤 + 实际 Java 代码块[串行] 或 [并行-N]（N=分组号，同组可并行）[并行-N] 组[串行]，按依赖排先后写完计划后逐条检查：
修复后直接完成，无需再审。
返回 docs/feature/YYYY-MM-DD-<feature-slug>/03-plan.md 的路径给 Master。到此停止。