メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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 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 | clarify-requirement |
| description | 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. |
把所有疑问一次性写入需求讨论文档。不写一行代码。
用：
不用：
先探索项目上下文，再把所有疑问一次性写入 docs/feature/YYYY-MM-DD-<feature-slug>/01-requirement.md。
文档格式： 严格遵循 ./requirement-template.md。目录路径和文件编号不可变动。
./requirement-template.md 格式，把所有问题批量写入 01-requirement.md。聚焦目的、约束、成功标准。优先出选择题（A/B/C）。一行一个问题。问题的维度由探索结果自然决定，不预设分类。00-overview.md（一句话概述今天确定了什么），再写 📋 需求总结 到 01-requirement.md 末尾。docs/feature/YYYY-MM-DD-<feature-slug>/（用当天日期）00-overview.md、01-requirement.md、02-design.md、03-plan.md