planner
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePlanner Skill
Planner Skill
Two workflows: planning (13-step plan creation + review) and execution
(implement plans).
包含两种工作流:规划(13步计划创建+审核)和执行(计划落地)。
Activation
激活条件
When this skill activates, IMMEDIATELY invoke the corresponding script. The
script IS the workflow.
| Mode | Intent | Command |
|---|---|---|
| planning | "plan", "design", "architect" | |
| execution | "execute", "implement", "run plan" | |
当该技能被激活时,立即调用对应的脚本。脚本即工作流本身。
| 模式 | 触发意图 | 命令 |
|---|---|---|
| planning | "plan"、"design"、"architect" | |
| execution | "execute"、"implement"、"run plan" | |
When to Use
使用场景
Use when task has:
- Multiple milestones with dependencies
- Architectural decisions requiring documentation
- Complexity benefiting from forced reflection pauses
Skip when task is:
- Single-step with obvious implementation
- Quick fix or minor change
- Already well-specified by user
当任务具备以下特征时使用:
- 存在多个相互依赖的里程碑
- 架构决策需要文档记录
- 复杂度较高,需要强制暂停以进行反思
当任务属于以下情况时跳过:
- 单步骤且实现方式明确
- 快速修复或微小变更
- 用户已提供详细明确的需求
Resources
参考资源
| Resource | Contents | Read When |
|---|---|---|
| Unified diff specification | Writing code changes in milestones |
| Plan template structure | Completing planning phase (injected by script) |
| Comment hygiene heuristics | Writing comments in code snippets |
| Structural conventions | Making decisions without explicit user guidance |
| 资源路径 | 内容概述 | 适用场景 |
|---|---|---|
| 统一diff规范 | 在里程碑中编写代码变更时参考 |
| 计划模板结构 | 完成规划阶段时使用(由脚本自动注入) |
| 注释编写优化指南 | 在代码片段中编写注释时参考 |
| 结构规范 | 在无用户明确指导时进行决策参考 |
Planning Workflow (13 steps)
规划工作流(13步)
Steps 1-5: Planning
- Context Discovery - explore, gather requirements
- Testing Strategy Discovery - identify test patterns
- Approach Generation - generate options with tradeoffs
- Assumption Surfacing - user confirmation of choices
- Approach Selection & Milestones - decide, write milestones + Code Intent
Steps 6-13: Review
- QR-Completeness - validate plan structure
- Gate - route based on QR result
- Developer Fills Diffs - convert Code Intent to diffs
- QR-Code - validate diffs and code quality
- Gate - route based on QR result
- TW Documentation Scrub - clean comments, inject WHY
- QR-Docs - validate comment hygiene
- Gate - PLAN APPROVED
步骤1-5:规划阶段
- 上下文探索 - 调研、收集需求
- 测试策略探索 - 确定测试模式
- 方案生成 - 生成带权衡分析的多种选项
- 假设明确 - 请用户确认选择
- 方案选择与里程碑制定 - 确定方案,编写里程碑+代码意图
步骤6-13:审核阶段
- QR完整性检查 - 验证计划结构
- Gate环节 - 根据QR结果决定后续路径
- 开发者编写Diff - 将代码意图转换为diff内容
- QR代码检查 - 验证diff和代码质量
- Gate环节 - 根据QR结果决定后续路径
- TW文档梳理 - 优化注释,补充设计原因(WHY)
- QR文档检查 - 验证注释规范
- Gate环节 - 计划获批
Execution Workflow (9 steps)
执行工作流(9步)
- Execution planning - wave analysis
- Reconciliation (conditional) - validate existing code
- Implementation - wave-aware parallel dispatch to developers
- Code QR - verify code quality (RULE 0/1/2)
- Code QR Gate - route to step 3 on fail
- Documentation - create CLAUDE.md/README.md
- Doc QR - verify documentation quality
- Doc QR Gate - route to step 6 on fail
- Retrospective - summary presentation
Scripts inject step-specific guidance. Invoke and follow output.
- 执行规划 - 阶段分析
- 一致性校验(可选) - 验证现有代码
- 落地实现 - 基于阶段分析并行分配给开发者
- 代码QR检查 - 验证代码质量(遵循RULE 0/1/2)
- 代码QR Gate环节 - 失败则返回步骤3
- 文档编写 - 创建CLAUDE.md/README.md
- 文档QR检查 - 验证文档质量
- 文档QR Gate环节 - 失败则返回步骤6
- 回顾总结 - 成果展示
脚本会注入各步骤的专属指导。请调用脚本并遵循其输出内容。