菜单
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.
用 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 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.
| name | review-docs |
| description | 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. |
对照上游文档审查下游文档的覆盖性、一致性、可行性。不审代码，只审文档。
| 维度 | 检查什么 |
|---|---|
| 覆盖性 | 上游文档的要求全部覆盖了吗？有无遗漏？ |
| 一致性 | 各部分之间有无矛盾？与上游文档一致吗？ |
| 可行性 | 技术方案在当前架构下能实现吗？有忽略的限制吗？ |
| 清晰度 | 有歧义吗？两处描述同一个东西名字/类型一致吗？ |
| 并行正确性 | (仅审计划时) 并行标记合理吗？有所需未声明的共享依赖吗？ |
按 ./review-template.md 格式，保存审查报告到 01-requirement.md 同目录：
docs/feature/YYYY-MM-DD-<feature-slug>/02.5-review-compliance.mddocs/feature/YYYY-MM-DD-<feature-slug>/03.5-review-compliance.md每个问题标注：Critical（阻断）、Important（建议修）、Minor（可忽略）。报告开头必须有 Verdict 裁决字段（PASS / PASS_WITH_NOTES / BLOCKED）及各等级问题计数。