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
加载文件：
references/research-phase.md
可跳过场景： 已提供调研人员报告时

2. Codebase Understanding

2. 代码库理解

Load: 
references/codebase-understanding.md
Skip if: Provided with scout reports
加载文件：
references/codebase-understanding.md
可跳过场景： 已提供侦察报告时

3. Solution Design

3. 解决方案设计

Load: 
references/solution-design.md
加载文件：
references/solution-design.md

4. Plan Creation & Organization

4. 计划创建与整理

Load: 
references/plan-organization.md
加载文件：
references/plan-organization.md

5. Task Breakdown & Output Standards

5. 任务拆解与输出标准

Load: 
references/output-standards.md
加载文件：
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. 调研阶段 → 指派调研人员，调研技术方案
  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/
└── YYYYMMDD-HHmm-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/
└── YYYYMMDD-HHmm-plan-name/
    ├── research/
    │   ├── researcher-XX-report.md
    │   └── ...
    ├── reports/
    │   ├── XX-report.md
    │   └── ...
    ├── scout/
    │   ├── scout-XX-report.md
    │   └── ...
    ├── plan.md
    ├── phase-XX-phase-name-here.md
    └── ...

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.
  • 内容全面且具体
  • 考虑长期可维护性
  • 不确定时进行充分调研
  • 关注安全性与性能问题
  • 计划需详细到可供初级开发人员使用
  • 与现有代码库模式保持一致
谨记： 计划的质量决定了实施的成败。请确保计划全面，覆盖解决方案的所有方面。