菜单
Performs a structured code review of implemented features against the PRD and Tech Spec. Use after tasks are implemented and code needs quality validation. Don't use for QA testing, bug fixing, or implementation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generates a Product Requirements Document (PRD) from a feature prompt. Use when planning a new feature, starting a project, or when asked to create a PRD. Don't use for technical specifications, task breakdowns, or implementation.
Breaks down a PRD and Tech Spec into an ordered list of implementable tasks. Use when PRD and Tech Spec are ready and the next step is planning the implementation sequence. Don't use for creating PRDs, writing specs, or implementing code.
Generates a Technical Specification from an existing PRD. Use when a PRD is ready and the next step is to define architecture, APIs, data models, and implementation strategy. Don't use for requirements gathering, task breakdown, or implementation.
Fixes all bugs listed in a bugs.md file with root-cause analysis and regression tests. Use after QA has identified bugs that need fixing. Don't use for new features, code review, or QA testing.
Performs Quality Assurance on implemented features including E2E testing, accessibility checks, and requirements verification. Use after implementation and code review are done. Don't use for code review, implementation, or bug fixing.
Implements a single task from the task list, including code, tests, and checks. Use when tasks have been created and the next step is writing code. Don't use for creating PRDs, specs, task lists, or code review.
| name | run-review |
| description | Performs a structured code review of implemented features against the PRD and Tech Spec. Use after tasks are implemented and code needs quality validation. Don't use for QA testing, bug fixing, or implementation. |
You are an AI assistant specialized in Code Review.
Use git diff to analyze code changes Verify that the code follows the project rules ALL tests must pass before approving the review The implementation must follow the TechSpec and Tasks EXACTLY
./tasks/prd-[feature-name]/prd.md./tasks/prd-[feature-name]/techspec.md./tasks/prd-[feature-name]/tasks.mdtasks/prd-[feature]/).tasks/prd-[feature]/prd.mdtasks/prd-[feature]/techspec.mdtasks/prd-[feature]/tasks.mdCLAUDE.md to understand project conventions and rules.git diff (or git log for committed changes) to identify all code changes related to this feature.CLAUDE.mdtasks/prd-[feature]/review-report.md.