Back to Details

project-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Table of Contents

目录

Project Planning Skill

项目规划技能

Transform specification into implementation plan with architecture design and dependency-ordered tasks.
将需求规格转换为包含架构设计和按依赖排序任务的实施计划。

Delegation

职责委托

For detailed task planning workflows, this skill delegates to 
spec-kit:task-planning
as the canonical implementation. Use this skill for quick planning needs; use spec-kit for comprehensive project plans.
对于详细的任务规划工作流，本技能会委托
spec-kit:task-planning
作为标准实现。快速规划需求可使用本技能；完整项目规划请使用spec-kit。

When To Use

适用场景

  • After specification phase completes
  • Need to design system architecture
  • Need task breakdown for implementation
  • Planning sprints and resource allocation
  • Converting requirements into actionable tasks
  • Defining component interfaces and dependencies
  • 需求规格阶段完成后
  • 需要设计系统架构
  • 需要拆分实施任务
  • 规划Sprint和资源分配
  • 将需求转换为可执行任务
  • 定义组件接口和依赖关系

When NOT To Use

不适用场景

  • No specification exists yet (use 
    Skill(attune:project-specification)
    first)
  • Still exploring problem space (use 
    Skill(attune:project-brainstorming)
    instead)
  • Ready to execute existing plan (use 
    Skill(attune:project-execution)
    instead)
  • Need to adjust running project (update plan incrementally, don't restart)
  • 暂无需求规格说明（请先使用
    Skill(attune:project-specification)
    ）
  • 仍在问题空间探索阶段（请改用
    Skill(attune:project-brainstorming)
    ）
  • 准备执行现有计划（请改用
    Skill(attune:project-execution)
    ）
  • 需要调整正在进行的项目（请增量更新计划，不要重启规划流程）

Integration

集成说明

With superpowers:
  • Uses 
    Skill(superpowers:writing-plans)
    for structured planning
  • Applies checkpoint-based execution patterns
  • Uses dependency analysis framework
Without superpowers:
  • Standalone planning methodology
  • Task breakdown templates
  • Dependency tracking patterns
搭配superpowers使用：
  • 调用
    Skill(superpowers:writing-plans)
    实现结构化规划
  • 应用基于检查点的执行模式
  • 使用依赖分析框架
独立使用：
  • 独立规划方法论
  • 任务拆分模板
  • 依赖追踪模式

Planning Phases

规划阶段

Phase 1: Architecture Design

阶段1：架构设计

Activities:
  1. Identify system components
  2. Define component responsibilities
  3. Design interfaces between components
  4. Map data flows
  5. Select technologies
Output: Architecture documentation with diagrams
活动内容：
  1. 识别系统组件
  2. 定义组件职责
  3. 设计组件间接口
  4. 梳理数据流
  5. 选型技术栈
输出：带示意图的架构文档

Phase 2: Task Breakdown

阶段2：任务拆分

Activities:
  1. Decompose FRs into implementation tasks
  2. Add testing tasks for each FR
  3. Add infrastructure tasks
  4. Add documentation tasks
  5. Estimate each task
Output: Task list with estimates
活动内容：
  1. 将功能需求（FR）拆分为实施任务
  2. 为每个功能需求添加测试任务
  3. 添加基础设施相关任务
  4. 添加文档相关任务
  5. 估算每个任务的工作量
输出：带工作量估算的任务列表

Phase 3: Dependency Analysis

阶段3：依赖分析

Activities:
  1. Identify task dependencies
  2. Create dependency graph
  3. Identify critical path
  4. Detect circular dependencies
  5. Optimize for parallelization
Output: Dependency-ordered task execution plan
活动内容：
  1. 识别任务依赖关系
  2. 生成依赖图谱
  3. 识别关键路径
  4. 检测循环依赖
  5. 优化任务支持并行执行
输出：按依赖排序的任务执行计划

Phase 4: Sprint Planning

阶段4：Sprint规划

Activities:
  1. Group tasks into sprints
  2. Balance sprint workload
  3. Identify milestones
  4. Plan releases
  5. Allocate resources
Output: Sprint schedule with milestones
活动内容：
  1. 将任务分组到不同Sprint
  2. 平衡Sprint工作量
  3. 确定里程碑
  4. 规划发布节奏
  5. 分配资源
输出：带里程碑的Sprint日程表

Architecture Design Patterns

架构设计模式

Component Identification

组件识别

Questions:
  • What are the major functional areas?
  • What concerns should be separated?
  • What components can be developed independently?
  • What components can be reused?
Common Patterns:
  • Frontend/Backend: Separate UI from business logic
  • API Layer: Separate interface from implementation
  • Data Layer: Separate data access from business logic
  • Integration Layer: Isolate external dependencies
参考问题：
  • 核心功能域有哪些？
  • 哪些关注点需要分离？
  • 哪些组件可以独立开发？
  • 哪些组件可以复用？
常见模式：
  • 前端/后端：将UI与业务逻辑分离
  • API层：将接口与实现分离
  • 数据层：将数据访问与业务逻辑分离
  • 集成层：隔离外部依赖

Component Template

组件模板

markdown
undefined
markdown
undefined

Component: [Name]

Component: [Name]

Responsibility: [What this component does]
Technology: [Stack and tools]
Interfaces:
Dependencies:
  • [Component 1]: [What's needed]
  • [Component 2]: [What's needed]
Data:
  • [Data structure 1]
  • [Data structure 2]
Configuration:
  • [Config param 1]
  • [Config param 2]
undefined
Responsibility: [What this component does]
Technology: [Stack and tools]
Interfaces:
Dependencies:
  • [Component 1]: [What's needed]
  • [Component 2]: [What's needed]
Data:
  • [Data structure 1]
  • [Data structure 2]
Configuration:
  • [Config param 1]
  • [Config param 2]
undefined

Task Breakdown Template

任务拆分模板

markdown
undefined
markdown
undefined

TASK-[XXX]: [Task Name]

TASK-[XXX]: [Task Name]

Description: [What needs to be done]
Type: Implementation | Testing | Documentation | Infrastructure | Deployment Priority: P0 (Critical) | P1 (High) | P2 (Medium) | P3 (Low) Estimate: [Story points or hours] Dependencies: TASK-XXX, TASK-YYY Sprint: Sprint N Assignee: [Name or TBD]
Linked Requirements: FR-XXX, NFR-YYY
Acceptance Criteria:
  • [Criterion 1]
  • [Criterion 2]
  • Tests passing
  • Documentation updated
Technical Notes:
  • [Implementation detail 1]
  • [Implementation detail 2]
Testing Requirements:
  • Unit tests: [What to test]
  • Integration tests: [What to test]
  • E2E tests: [What to test]
Definition of Done:
  • Code complete
  • Tests passing
  • Code reviewed
  • Documentation updated
  • Deployed to staging
undefined
Description: [What needs to be done]
Type: Implementation | Testing | Documentation | Infrastructure | Deployment Priority: P0 (Critical) | P1 (High) | P2 (Medium) | P3 (Low) Estimate: [Story points or hours] Dependencies: TASK-XXX, TASK-YYY Sprint: Sprint N Assignee: [Name or TBD]
Linked Requirements: FR-XXX, NFR-YYY
Acceptance Criteria:
  • [Criterion 1]
  • [Criterion 2]
  • Tests passing
  • Documentation updated
Technical Notes:
  • [Implementation detail 1]
  • [Implementation detail 2]
Testing Requirements:
  • Unit tests: [What to test]
  • Integration tests: [What to test]
  • E2E tests: [What to test]
Definition of Done:
  • Code complete
  • Tests passing
  • Code reviewed
  • Documentation updated
  • Deployed to staging
undefined

Task Estimation Guidelines

任务估算指南

Story Points (Fibonacci):
  • 1 point: < 2 hours, trivial, well-understood
  • 2 points: 2-4 hours, straightforward
  • 3 points: 4-8 hours, some complexity
  • 5 points: 1-2 days, moderate complexity
  • 8 points: 2-3 days, significant complexity
  • 13 points: 3-5 days, high complexity (consider breaking down)
  • 21 points: > 5 days, very complex (MUST break down)
Factors to consider:
  • Technical complexity
  • Uncertainty/unknowns
  • Dependencies on other work
  • Testing requirements
  • Documentation needs
故事点（斐波那契数列）：
  • 1点：< 2小时，非常简单，需求完全明确
  • 2点：2-4小时，流程清晰
  • 3点：4-8小时，存在一定复杂度
  • 5点：1-2天，中等复杂度
  • 8点：2-3天，复杂度较高
  • 13点：3-5天，复杂度高（建议拆分）
  • 21点：> 5天，复杂度极高（必须拆分）
估算参考因素：
  • 技术复杂度
  • 不确定性/未知问题
  • 对其他工作的依赖
  • 测试要求
  • 文档需求

Dependency Graph

依赖图谱

Notation:
TASK-001 (Foundation)
    ├─▶ TASK-002 (Database schema)
    │       ├─▶ TASK-003 (Models)
    │       └─▶ TASK-011 (Data import)
    └─▶ TASK-004 (Authentication)
            └─▶ TASK-005 (Auth middleware)
                    └─▶ TASK-010 (Protected endpoints)
Validation:
  • No circular dependencies (A depends on B, B depends on A)
  • Critical path identified
  • Parallel work opportunities identified
  • Blocking tasks highlighted
表示方法：
TASK-001 (Foundation)
    ├─▶ TASK-002 (Database schema)
    │       ├─▶ TASK-003 (Models)
    │       └─▶ TASK-011 (Data import)
    └─▶ TASK-004 (Authentication)
            └─▶ TASK-005 (Auth middleware)
                    └─▶ TASK-010 (Protected endpoints)
校验规则：
  • 无循环依赖（A依赖B，B依赖A）
  • 关键路径已识别
  • 可并行执行的任务已识别
  • 阻塞性任务已标记

Sprint Structure

Sprint结构

Sprint Template:
markdown
undefined
Sprint模板：
markdown
undefined

Sprint [N]: [Focus Area]

Sprint [N]: [Focus Area]

Dates: [Start] - [End] Goal: [Sprint objective] Capacity: [Team capacity in story points]
Dates: [Start] - [End] Goal: [Sprint objective] Capacity: [Team capacity in story points]

Planned Tasks ([X] story points)

Planned Tasks ([X] story points)

  • TASK-XXX ([N] points)
  • TASK-YYY ([M] points)
  • ...
  • TASK-XXX ([N] points)
  • TASK-YYY ([M] points)
  • ...

Deliverable

Deliverable

[What will be demonstrable at sprint end]
[What will be demonstrable at sprint end]

Risks

Risks

  • [Risk 1 with mitigation]
  • [Risk 2 with mitigation]
  • [Risk 1 with mitigation]
  • [Risk 2 with mitigation]

Dependencies

Dependencies

  • [External dependency 1]
  • [External dependency 2]
undefined
  • [External dependency 1]
  • [External dependency 2]
undefined

Risk Assessment

风险评估

Risk Template:
markdown
| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
| [Risk description] | High/Med/Low | High/Med/Low | [How to address] |
Common Risks:
  • Technology unknowns
  • Third-party API dependencies
  • Resource availability
  • Scope creep
  • Performance issues
  • Security vulnerabilities
风险模板：
markdown
| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|
| [Risk description] | High/Med/Low | High/Med/Low | [How to address] |
常见风险：
  • 技术未知问题
  • 第三方API依赖
  • 资源可用性
  • 范围蔓延
  • 性能问题
  • 安全漏洞

Output Format

输出格式

Save to 
docs/implementation-plan.md
:
markdown
undefined
保存到
docs/implementation-plan.md
：
markdown
undefined

[Project Name] - Implementation Plan v[version]

[Project Name] - Implementation Plan v[version]

Author: [Name] Date: [YYYY-MM-DD] Sprint Length: [Duration] Team Size: [Number] Target Completion: [Date]
Author: [Name] Date: [YYYY-MM-DD] Sprint Length: [Duration] Team Size: [Number] Target Completion: [Date]

Architecture

Architecture

System Overview

System Overview

[High-level architecture description]
[High-level architecture description]

Component Diagram

Component Diagram

[ASCII or markdown diagram]
[ASCII or markdown diagram]

Components

Components

[Component details using template above]
[Component details using template above]

Data Flow

Data Flow

[How data moves through system]
[How data moves through system]

Task Breakdown

Task Breakdown

Phase 1: [Name] (Sprint [N]) - TASK-001 through TASK-010

Phase 1: [Name] (Sprint [N]) - TASK-001 through TASK-010

[Tasks using template above]
[Tasks using template above]

Phase 2: [Name] (Sprint [M]) - TASK-011 through TASK-020

Phase 2: [Name] (Sprint [M]) - TASK-011 through TASK-020

[Tasks using template above]
[Tasks using template above]

Dependency Graph

Dependency Graph

[Dependency visualization]
[Dependency visualization]

Sprint Schedule

Sprint Schedule

[Sprint details using template above]
[Sprint details using template above]

Risk Assessment

Risk Assessment

[Risk table]
[Risk table]

Success Metrics

Success Metrics

  • [Metric 1]
  • [Metric 2]
  • [Metric 1]
  • [Metric 2]

Timeline

Timeline

SprintDatesFocusDeliverable
1Jan 3-16FoundationDev environment
2Jan 17-30CoreFeature X working
SprintDatesFocusDeliverable
1Jan 3-16FoundationDev environment
2Jan 17-30CoreFeature X working

Next Steps

Next Steps

  1. Review plan with team
  2. Initialize project with 
    /attune:project-init
  3. Start execution with 
    /attune:execute
undefined
  1. Review plan with team
  2. Initialize project with 
    /attune:project-init
  3. Start execution with 
    /attune:execute
undefined

Quality Checks

质量检查

Before completing plan:
  • ✅ All architecture components documented
  • ✅ All FRs mapped to tasks
  • ✅ All tasks have acceptance criteria
  • ✅ Dependencies are acyclic
  • ✅ Effort estimates provided
  • ✅ Critical path identified
  • ✅ Risks assessed with mitigations
  • ✅ Sprints balanced by capacity
完成规划前需确认：
  • ✅ 所有架构组件已完成文档记录
  • ✅ 所有功能需求已映射到对应任务
  • ✅ 所有任务都有验收标准
  • ✅ 依赖无循环
  • ✅ 已提供工作量估算
  • ✅ 关键路径已识别
  • ✅ 已评估风险并给出缓解方案
  • ✅ Sprint工作量与团队容量匹配

Post-Completion: Workflow Continuation (REQUIRED)

完成后：工作流接续（必填）

Automatic Trigger: After Quality Checks pass and 
docs/implementation-plan.md
is saved, MUST auto-invoke the next phase.
When continuation is invoked:
  1. Verify 
    docs/implementation-plan.md
    exists and is non-empty
  2. Display checkpoint message to user: 
    Implementation plan complete. Saved to docs/implementation-plan.md.
Proceeding to execution phase...
  3. Invoke next phase: 
    Skill(attune:project-execution)
Bypass Conditions (ONLY skip continuation if ANY true):
  • --standalone
    flag was provided by the user
  • docs/implementation-plan.md
    does not exist or is empty (phase failed)
  • User explicitly requests to stop after planning
Do NOT prompt the user for confirmation — this is a lightweight checkpoint, not an interactive gate. The user can always interrupt if needed.
自动触发：质量检查通过且
docs/implementation-plan.md
保存后，必须自动调用下一阶段。
接续流程触发时：
  1. 校验
    docs/implementation-plan.md
    存在且非空
  2. 向用户展示检查点消息： 
    实施计划已完成，已保存到 docs/implementation-plan.md。
正在进入执行阶段...
  3. 调用下一阶段： 
    Skill(attune:project-execution)
跳过条件：满足任意一项即可跳过接续流程：
  • 用户提供了
    --standalone
    参数
  • docs/implementation-plan.md
    不存在或为空（阶段执行失败）
  • 用户明确要求规划完成后停止
无需向用户确认——这是轻量级检查点，而非交互式关卡。用户如有需要可随时中断流程。

Related Skills

相关技能

  • Skill(superpowers:writing-plans)
    - Planning methodology (if available)
  • Skill(spec-kit:task-planning)
    - Task breakdown (if available)
  • Skill(attune:project-specification)
    - Previous phase
  • Skill(attune:project-execution)
    - AUTO-INVOKED next phase after planning
  • Skill(attune:mission-orchestrator)
    - Full lifecycle orchestration
  • Skill(superpowers:writing-plans)
    - 规划方法论（如有）
  • Skill(spec-kit:task-planning)
    - 任务拆分（如有）
  • Skill(attune:project-specification)
    - 上一阶段
  • Skill(attune:project-execution)
    - 自动调用规划完成后的下一阶段
  • Skill(attune:mission-orchestrator)
    - 全生命周期编排

Related Commands

相关命令

  • /attune:blueprint
    - Invoke this skill
  • /attune:execute
    - Next step in workflow
  • /attune:blueprint
    - 调用本技能
  • /attune:execute
    - 工作流下一步

Examples

示例

See 
/attune:blueprint
command documentation for complete examples.
完整示例请查看
/attune:blueprint
命令文档。

Troubleshooting

问题排查

Common Issues

常见问题

If you find circular dependencies in your task graph, break one of the tasks into smaller sub-tasks. If sprint capacity is consistently exceeded, re-estimate tasks using the Fibonacci scale or reduce sprint scope.
如果任务图谱中存在循环依赖，请将其中一个任务拆分为更小的子任务。如果Sprint容量持续超出，请使用斐波那契量表重新估算任务，或者缩小Sprint范围。