plan-review
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCRITICAL: Do NOT usetool — it blocks Write/Edit/Task tools. Follow the workflow below.EnterPlanMode
重要提示： 请勿使用工具——它会阻止Write/Edit/Task工具。请遵循以下工作流程。EnterPlanMode
Your Mission
你的任务
Critically self-review the implementation plan to ensure quality before coding begins.
在编码开始前，对实施计划进行严格的自我评审，以确保质量。
Plan Resolution
计划解析
- If provided → Use that path
$ARGUMENTS - Else check → Use active plan path
## Plan Context - If no plan found → Error: run first
/plan
- 若提供了→ 使用该路径
$ARGUMENTS - 否则检查→ 使用当前激活的计划路径
## Plan Context - 若未找到计划 → 错误：先运行
/plan
Review Checklist
评审检查清单
| Category | Check |
|---|---|
| Structure | Has plan.md with YAML frontmatter (title, status, effort)? |
| Structure | Phases numbered and linked correctly? |
| Logic | Dependencies between phases mapped? |
| Logic | Risk assessment present with mitigations? |
| Patterns | Uses platform patterns (not custom solutions)? |
| Patterns | Files in correct project locations? |
| Completeness | Success criteria defined and measurable? |
| Completeness | All edge cases considered? |
| Best Practices | Follows YAGNI/KISS/DRY principles? |
| Best Practices | No over-engineering or premature abstraction? |
| 类别 | 检查项 |
|---|---|
| 结构 | 是否包含带有YAML前置元数据（标题、状态、工作量）的plan.md文件？ |
| 结构 | 阶段是否已编号且链接正确？ |
| 逻辑 | 是否梳理了各阶段之间的依赖关系？ |
| 逻辑 | 是否包含风险评估及缓解措施？ |
| 模式 | 是否采用平台既定模式（而非自定义解决方案）？ |
| 模式 | 文件是否存放于项目的正确位置？ |
| 完整性 | 是否定义了可衡量的成功标准？ |
| 完整性 | 是否考虑了所有边缘情况？ |
| 最佳实践 | 是否遵循YAGNI/KISS/DRY原则？ |
| 最佳实践 | 是否存在过度设计或过早抽象的问题？ |
Review Process
评审流程
- Read plan.md and all phase-*.md files
- Evaluate each checklist item
- Identify issues with specific locations and fixes
- Output approval or revision requirements
- 阅读 plan.md及所有phase-*.md文件
- 评估 检查清单中的每一项
- 识别 问题的具体位置并给出修复建议
- 输出 批准结果或修订要求
Output Format
输出格式
If Plan Passes:
✅ Plan Review: APPROVED
- Structure: Valid
- Logic: Sound
- Patterns: Compliant
- Completeness: Adequate
- Best Practices: Followed
Proceeding to implementation...If Issues Found:
⚠️ Plan Review: NEEDS REVISION
Issues:
1. [Category] [File:Line] Issue description → Fix suggestion
2. [Category] [File:Line] Issue description → Fix suggestion
Update plan before proceeding.若计划通过：
✅ Plan Review: APPROVED
- Structure: Valid
- Logic: Sound
- Patterns: Compliant
- Completeness: Adequate
- Best Practices: Followed
Proceeding to implementation...若发现问题：
⚠️ Plan Review: NEEDS REVISION
Issues:
1. [Category] [File:Line] Issue description → Fix suggestion
2. [Category] [File:Line] Issue description → Fix suggestion
Update plan before proceeding.IMPORTANT Task Planning Notes
重要的任务规划注意事项
- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed
- 始终进行规划，并拆分为多个小型待办任务
- 始终添加一个最终评审待办任务，在结束时评审已完成的工作，以确定是否需要修复或改进
Important Notes
重要提示
- Focus on major issues that would impact implementation
- Don't nitpick formatting or style unless it affects clarity
- If plan is simple and solid, approve quickly
- Always provide actionable fix suggestions for issues
- 重点关注会影响实施的重大问题
- 除非影响清晰度，否则不要纠结于格式或风格细节
- 若计划简洁且可靠，可快速批准
- 始终为问题提供可执行的修复建议