メニュー
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.
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 when technical design is complete and approved, to produce a bite-sized implementation plan with exact file paths, code, and commands.
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 | design-feature |
| description | 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. |
在需求澄清完成后，产出技术设计文档。不写代码，只出设计。
用：
不用：
AGENTS.md，理解项目的架构约定、命名规范、包结构、通信方式（Feign/RocketMQ）。docs/feature/当次日期/01-requirement.md，尤其是 📋 需求总结。docs/feature/YYYY-MM-DD-<feature-slug>/02-design.md。遵循 ./design-template.md。路径和文件编号不可变动。
必须覆盖每一项：架构、组件/模块划分、数据模型、数据流、错误处理、测试策略。每个组件要能回答：做什么、怎么用、依赖谁。每个组件应可独立理解和测试。
写完文档后逐条检查：
修改后直接进入下一步，无需再审。
返回 docs/feature/YYYY-MM-DD-<feature-slug>/02-design.md 的路径给 Master。到此停止。