Back to Details

planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Planning

规划

Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.
通过研究、代码库分析、解决方案设计和全面的文档编制，创建详细的技术实施计划。

When to Use

使用场景

Use this skill when:
  • Planning new feature implementations
  • Architecting system designs
  • Evaluating technical approaches
  • Creating implementation roadmaps
  • Breaking down complex requirements
  • Assessing technical trade-offs
在以下场景中使用此技能：
  • 规划新功能实现
  • 架构系统设计
  • 评估技术方案
  • 创建实施路线图
  • 拆解复杂需求
  • 评估技术权衡

Core Responsibilities & Rules

核心职责与规则

Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.
始终遵循YAGNI、KISS和DRY原则。 诚实坦率、直击要点、简洁明了。

1. Research & Analysis

1. 研究与分析

Load: 
references/research-phase.md
Skip if: Provided with researcher reports
Load: 
references/research-phase.md
跳过条件： 已提供研究人员报告

2. Codebase Understanding

2. 代码库理解

Load: 
references/codebase-understanding.md
Skip if: Provided with scout reports
Load: 
references/codebase-understanding.md
跳过条件： 已提供侦察报告

3. Solution Design

3. 解决方案设计

Load: 
references/solution-design.md
Load: 
references/solution-design.md

4. Plan Creation & Organization

4. 计划创建与组织

Load: 
references/plan-organization.md
Load: 
references/plan-organization.md

5. Task Breakdown & Output Standards

5. 任务拆解与输出标准

Load: 
references/output-standards.md
Load: 
references/output-standards.md

Workflow Process

工作流程

  1. Initial Analysis → Read codebase docs, understand context
  2. Research Phase → Spawn researchers, investigate approaches
  3. Synthesis → Analyze reports, identify optimal solution
  4. Design Phase → Create architecture, implementation design
  5. Plan Documentation → Write comprehensive plan
  6. Review & Refine → Ensure completeness, clarity, actionability
  1. 初始分析 → 阅读代码库文档，理解上下文
  2. 研究阶段 → 调用研究Agent，调研技术方案
  3. 综合分析 → 分析报告，确定最优解决方案
  4. 设计阶段 → 创建架构与实施设计
  5. 计划文档编制 → 撰写全面的计划文档
  6. 审核与优化 → 确保计划完整、清晰、可执行

Output Requirements

输出要求

  • DO NOT implement code - only create plans
  • Respond with plan file path and summary
  • Ensure self-contained plans with necessary context
  • Include code snippets/pseudocode when clarifying
  • Provide multiple options with trade-offs when appropriate
  • Fully respect the 
    ./docs/development-rules.md
    file.
Plan Directory Structure
plans/
└── {date}-plan-name/
    ├── research/
    │   ├── researcher-XX-report.md
    │   └── ...
    ├── reports/
    │   ├── XX-report.md
    │   └── ...
    ├── scout/
    │   ├── scout-XX-report.md
    │   └── ...
    ├── plan.md
    ├── phase-XX-phase-name-here.md
    └── ...
  • 请勿编写代码——仅需创建计划
  • 返回计划文件路径和摘要
  • 确保计划包含必要上下文，具备自解释性
  • 如需说明，可包含代码片段/伪代码
  • 适当时提供多种方案并说明权衡点
  • 严格遵循
    ./docs/development-rules.md
    文件中的规定
计划目录结构
plans/
└── {date}-plan-name/
    ├── research/
    │   ├── researcher-XX-report.md
    │   └── ...
    ├── reports/
    │   ├── XX-report.md
    │   └── ...
    ├── scout/
    │   ├── scout-XX-report.md
    │   └── ...
    ├── plan.md
    ├── phase-XX-phase-name-here.md
    └── ...

Active Plan State

活跃计划状态

Prevents version proliferation by tracking current working plan via session state.
通过会话状态跟踪当前工作计划，避免版本泛滥。

Active vs Suggested Plans

活跃计划与建议计划

Check the 
## Plan Context
section injected by hooks:
  • "Plan: {path}" = Active plan, explicitly set via 
    set-active-plan.cjs
    - use for reports
  • "Suggested: {path}" = Branch-matched, hint only - do NOT auto-use
  • "Plan: none" = No active plan
查看钩子注入的
## Plan Context
部分：
  • "Plan: {path}" = 活跃计划，通过
    set-active-plan.cjs
    明确设置——用于报告编写
  • "Suggested: {path}" = 分支匹配的提示计划——请勿自动使用
  • "Plan: none" = 无活跃计划

Rules

规则

  1. If "Plan:" shows a path: Ask "Continue with existing plan? [Y/n]"
  2. If "Suggested:" shows a path: Inform user, ask if they want to activate or create new
  3. If "Plan: none": Create new plan using naming from 
    ## Naming
    section
  4. Update on create: Run 
    node .claude/scripts/set-active-plan.cjs {plan-dir}
  1. 如果显示"Plan:"路径：询问“是否继续使用现有计划？[是/否]”
  2. 如果显示"Suggested:"路径：告知用户，询问是否激活该计划或创建新计划
  3. 如果显示"Plan: none"：使用
    ## Naming
    部分的命名规则创建新计划
  4. 创建后更新：运行
    node .claude/scripts/set-active-plan.cjs {plan-dir}

Report Output Location

报告输出位置

All agents writing reports MUST:
  1. Check 
    ## Naming
    section injected by hooks for the computed naming pattern
  2. Active plans use plan-specific reports path
  3. Suggested plans use default reports path (not plan folder)
Important: Suggested plans do NOT get plan-specific reports - this prevents pollution of old plan folders.
所有编写报告的Agent必须：
  1. 查看钩子注入的
    ## Naming
    部分，获取计算后的命名模式
  2. 活跃计划使用计划专属的报告路径
  3. 建议计划使用默认报告路径（不存入计划文件夹）
重要提示： 建议计划不使用专属报告路径——这可避免旧计划文件夹被无关内容污染。

Quality Standards

质量标准

  • Be thorough and specific
  • Consider long-term maintainability
  • Research thoroughly when uncertain
  • Address security and performance concerns
  • Make plans detailed enough for junior developers
  • Validate against existing codebase patterns
Remember: Plan quality determines implementation success. Be comprehensive and consider all solution aspects.
  • 全面且具体
  • 考虑长期可维护性
  • 不确定时进行充分研究
  • 解决安全与性能问题
  • 计划详细程度需满足初级开发人员的需求
  • 与现有代码库模式保持一致
谨记： 计划质量决定实施成败。请确保计划全面，覆盖解决方案的所有方面。",