一键导入
review-implementation
Use when implementation phase is complete -- verifies code matches spec, identifies gaps, and tracks completion state
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when implementation phase is complete -- verifies code matches spec, identifies gaps, and tracks completion state
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when reviewing a spec or task graph for completeness before implementation
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when decomposing a spec, design, or feature description into a task dependency graph with self-evaluating acceptance criteria
Use when doing creative product, feature, component, functionality, or behavior design work
Use when infrastructure or features are built but before declaring done -- verifies work is wired into the system and actively used
| name | review-implementation |
| description | Use when implementation phase is complete -- verifies code matches spec, identifies gaps, and tracks completion state |
Compare code against the plan/spec line by line. Report what's done, what's missing, and what diverged.
Find the source of truth — plan file, issue description, or requirements doc. If none exists, ask before proceeding.
Extract every requirement, acceptance criterion, and edge case from the spec into a flat checklist.
For each checklist item:
Read the actual code. Do not infer from file names or function signatures.
## Implementation Review: [feature/scope]
### Summary
X/Y requirements met | Z gaps | W divergences
### Checklist
- [x] Requirement A — `src/foo.py:42`
- [~] Requirement B — partial, missing error handling
- [ ] Requirement C — not implemented
- [!] Requirement D — diverged: spec says X, code does Y
### Gaps (action needed)
1. [description + suggested fix or issue]
### Intentional Divergences (confirm with user)
1. [what changed and why it might be fine]