Back to Details

milestone-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Milestone Planning

里程碑规划

Purpose

目标

Build milestone plans that are dependency-aware, risk-aware, and tied to real delivery outcomes.
构建具备依赖感知、风险感知且与实际交付成果挂钩的里程碑计划。

Use When

适用场景

  • entering pre-production or production
  • scope has changed materially
  • the team needs a realistic plan instead of a loose backlog
  • 进入预生产或生产阶段
  • 范围发生重大变更
  • 团队需要一份切合实际的计划而非松散的待办事项列表

Inputs

输入项

  • current scope
  • team capacity
  • dependencies
  • risk register
  • technical and content constraints
  • 当前范围
  • 团队产能
  • 依赖关系
  • 风险登记册
  • 技术与内容约束

Process

流程

  1. define milestone purpose, entry criteria, and exit criteria
  2. break work into feature-sized deliverables with owners
  3. sequence dependencies and identify blockers early
  4. reserve capacity for integration, QA, and rework
  5. mark candidate descopes and optional stretch items
  1. 定义里程碑的目标、进入标准和退出标准
  2. 将工作拆解为具备负责人的功能级交付项
  3. 梳理依赖顺序，尽早识别阻塞点
  4. 预留整合、QA、和返工的产能
  5. 标记候选缩减范围项和可选拓展项

Outputs

输出成果

  • milestone plan
  • dependency map
  • ownership list
  • risk-aware scope breakdown
  • 里程碑计划
  • 依赖关系图
  • 负责人清单
  • 具备风险感知的范围拆解

Quality Bar

质量标准

  • each milestone has exit criteria a reviewer can check without interpretation
  • dependencies between workstreams are mapped before dates are committed
  • every milestone names its owner and the decision that unblocks the next one
  • risks carry probability, impact, and a named mitigation owner
  • 每个里程碑都有无需解读即可供审核者检查的退出标准
  • 在确定日期前，已梳理各工作流之间的依赖关系
  • 每个里程碑都明确其负责人以及解锁下一个里程碑的决策事项
  • 风险需包含发生概率、影响程度以及指定的缓解措施负责人

Common Failure Modes

常见失败模式

  • milestones defined by dates instead of demonstrable outcomes
  • hidden dependencies discovered mid-milestone, invalidating the schedule
  • "90% done" syndrome — no binary exit criteria to call a milestone complete
  • risk lists written once at kickoff and never re-reviewed
  • 里程碑按日期而非可验证成果定义
  • 在里程碑执行中期发现隐藏依赖，导致计划失效
  • “完成90%”综合征——没有明确的二元退出标准来判定里程碑是否完成
  • 风险清单仅在启动时编写一次，后续从未重新审核

Related Agents

相关Agent

  • producer
  • planner
  • technical-design-lead
  • producer
  • planner
  • technical-design-lead

Related Commands

相关命令

  • milestone-plan
  • plan
  • orchestrate
  • milestone-plan
  • plan
  • orchestrate

Notes

注意事项

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
  • 确保此skill与相关规则层及当前项目文档保持一致；
  • 如果引擎特定约束导致工作流程发生重大变更，请移交至匹配的引擎skill或引擎特定审核人员。