Back to Details

task-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Task Planning

任务规划

Overview

概述

Transforms specifications and implementation plans into actionable, dependency-ordered tasks. Creates phased breakdowns that guide systematic implementation.
将规格说明和落地计划转换为可执行的、按依赖关系排序的任务。创建分阶段拆解方案，指导系统化的落地实施。

When To Use

适用场景

  • Converting specifications to implementation tasks
  • Planning feature implementation order
  • Identifying parallel execution opportunities
  • Breaking down complex features into phases
  • 将规格说明转换为落地任务
  • 规划功能落地的执行顺序
  • 识别并行执行的机会
  • 将复杂功能拆解为多个阶段

When NOT To Use

不适用场景

  • Writing specifications - use spec-writing
  • 编写规格说明 - 请使用spec-writing

Task Phases

任务阶段

Tasks follow a 5-phase structure from setup through polish:
  • Phase 0: Setup - Project initialization, dependencies, configuration
  • Phase 1: Foundation - Data models, interfaces, test infrastructure
  • Phase 2: Core Implementation - Business logic, APIs, services
  • Phase 3: Integration - External services, middleware, logging
  • Phase 4: Polish - Optimization, documentation, final testing
For detailed phase definitions, selection guidelines, and anti-patterns, see 
modules/phase-structure.md
.
任务遵循从搭建到优化的5阶段结构：
  • 阶段0：搭建 - 项目初始化、依赖配置、环境设置
  • 阶段1：基础构建 - 数据模型、接口、测试基础设施
  • 阶段2：核心落地 - 业务逻辑、API、服务
  • 阶段3：集成 - 外部服务、中间件、日志
  • 阶段4：优化 - 性能调优、文档编写、最终测试
如需详细的阶段定义、选择指南和反模式，请查看
modules/phase-structure.md
。

Task Format

任务格式

Each task includes:
  • ID: Unique identifier (TASK-001)
  • Description: Clear action statement
  • Phase: Which phase it belongs to
  • Dependencies: Tasks that must complete first
  • Parallel Marker: [P] if can run concurrently
  • Files: Affected file paths
  • Criteria: How to verify completion
每个任务包含以下内容：
  • ID：唯一标识符（TASK-001）
  • 描述：清晰的行动说明
  • 阶段：所属阶段
  • 依赖项：必须先完成的前置任务
  • 并行标记：若可并发执行则标记[P]
  • 文件：受影响的文件路径
  • 验收标准：任务完成的验证方式

Dependency Rules

依赖规则

Dependencies define execution order and identify parallelization opportunities:
  • Sequential Tasks: Execute in strict order when dependencies exist
  • Parallel Tasks [P]: Can run concurrently when ALL nonconflicting conditions are met
  • File Coordination: Tasks affecting same files MUST run sequentially
Nonconflicting Criteria for Parallel Execution:
  • ✅ Files: No file overlap between tasks
  • ✅ State: No shared configuration or global state
  • ✅ Dependencies: All prerequisites satisfied
  • ✅ Code paths: No merge conflicts possible
  • ✅ Outputs: Tasks don't need each other's results
Mark tasks with [P] ONLY if they pass ALL criteria above.
For fan-out/fan-in patterns, task ID conventions, and validation rules, see 
modules/dependency-patterns.md
.
依赖关系定义了执行顺序，并识别并行执行的机会：
  • 顺序任务：存在依赖关系时，必须严格按顺序执行
  • 并行任务 [P]：当所有无冲突条件满足时，可并发执行
  • 文件协调：影响同一文件的任务必须按顺序执行
并行执行的无冲突标准：
  • ✅ 文件：任务之间无文件重叠
  • ✅ 状态：无共享配置或全局状态
  • ✅ 依赖：所有前置条件已满足
  • ✅ 代码路径：不会产生合并冲突
  • ✅ 输出：任务之间不需要彼此的结果
仅当任务满足以上所有标准时，才能标记为[P]。
如需了解扇出/扇入模式、任务ID约定和验证规则，请查看
modules/dependency-patterns.md
。

Example Task Entry

任务示例

markdown
undefined
markdown
undefined

Phase 2: Core Implementation

Phase 2: Core Implementation

TASK-007 - Implement user authentication service [P]

TASK-007 - Implement user authentication service [P]

Dependencies: TASK-003, TASK-004 Files: src/services/auth.ts, src/types/user.ts Criteria: All auth tests pass, tokens are valid JWT
**Verification:** Run `pytest -v` to verify tests pass.
Dependencies: TASK-003, TASK-004 Files: src/services/auth.ts, src/types/user.ts Criteria: All auth tests pass, tokens are valid JWT
**验证方式：** 运行`pytest -v`命令验证测试通过。

Quality Checklist

质量检查清单

  • All requirements mapped to tasks
  • Dependencies are explicit
  • Parallel opportunities identified
  • Tasks are right-sized (not too large/small)
  • Each task has clear completion criteria
  • 所有需求均映射到对应任务
  • 依赖关系明确
  • 已识别并行执行机会
  • 任务粒度合适（不过大或过小）
  • 每个任务都有清晰的验收标准

Related Skills

相关技能

  • spec-writing
    : Creating source specifications
  • speckit-orchestrator
    : Workflow coordination
  • spec-writing
    ：创建原始规格说明
  • speckit-orchestrator
    ：工作流协调

Troubleshooting

故障排查

Common Issues

常见问题

Command not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior Enable verbose logging with 
--verbose
flag
命令未找到 确保所有依赖已安装且在PATH路径中
权限错误 检查文件权限，使用适当权限运行
异常行为 使用
--verbose
flag启用详细日志