milestone-review

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Phase 0: Parse Arguments

阶段0：解析参数

Extract the milestone name (

current

or a specific name) and resolve the review mode (once, store for all gate spawns this run):

If
```
--review [full|lean|solo]
```
was passed → use that
Else read
```
production/review-mode.txt
```
→ use that value
Else → default to
```
lean
```

See

.claude/docs/director-gates.md

for the full check pattern.

提取里程碑名称（

current

或特定名称）并确定评审模式（单次执行，或为本次运行的所有检查点存储该模式）：

如果传入了
```
--review [full|lean|solo]
```
→ 使用该模式
否则读取
```
production/review-mode.txt
```
→ 使用该文件中的值
否则 → 默认使用
```
lean
```
模式

完整检查规则请参见

.claude/docs/director-gates.md

。

Phase 1: Load Milestone Data

阶段1：加载里程碑数据

Read the milestone definition from

production/milestones/

. If the argument is

current

, use the most recently modified milestone file.

Read all sprint reports for sprints within this milestone from

production/sprints/

从

production/milestones/

读取里程碑定义。如果参数为

current

，则使用最近修改的里程碑文件。

从

production/sprints/

读取该里程碑内所有迭代的迭代报告。

Phase 2: Scan Codebase Health

阶段2：扫描代码库健康状况

Scan for
```
TODO
```
,
```
FIXME
```
,
```
HACK
```
markers that indicate incomplete work
Check the risk register at
```
production/risk-register/
```

扫描
```
TODO
```
、
```
FIXME
```
、
```
HACK
```
标记，这些标记代表未完成的工作
检查
```
production/risk-register/
```
中的风险登记册

Phase 3: Generate the Milestone Review

阶段3：生成里程碑评审报告

markdown

undefined

markdown

undefined

Milestone Review: [Milestone Name]

里程碑评审：[里程碑名称]

Overview

概述

Target Date: [Date]
Current Date: [Today]
Days Remaining: [N]
Sprints Completed: [X/Y]

目标日期：[日期]
当前日期：[今日]
剩余天数：[N]
已完成迭代：[X/Y]

Feature Completeness

功能完整性

Fully Complete

完全完成

Feature	Acceptance Criteria	Test Status

功能	验收标准	测试状态

Partially Complete

部分完成

Feature	% Done	Remaining Work	Risk to Milestone

功能	完成率	剩余工作	对里程碑的风险

Not Started

未启动

Feature	Priority	Can Cut?	Impact of Cutting

功能	优先级	是否可裁剪	裁剪影响

Quality Metrics

质量指标

Open S1 Bugs: [N] -- [List]
Open S2 Bugs: [N]
Open S3 Bugs: [N]
Test Coverage: [X%]
Performance: [Within budget? Details]

未解决S1级Bug：[N] -- [列表]
未解决S2级Bug：[N]
未解决S3级Bug：[N]
测试覆盖率：[X%]
性能：[是否符合预算？详情]

Code Health

代码健康状况

TODO count: [N across codebase]
FIXME count: [N]
HACK count: [N]
Technical debt items: [List critical ones]

TODO数量：[全代码库共N个]
FIXME数量：[N]
HACK数量：[N]
技术债务项：[列出关键项]

Risk Assessment

风险评估

Risk	Status	Impact if Realized	Mitigation Status

风险	状态	发生后的影响	缓解措施状态

Velocity Analysis

速度分析

Planned vs Completed (across all sprints): [X/Y tasks = Z%]
Trend: [Improving / Stable / Declining]
Adjusted estimate for remaining work: [Days needed at current velocity]

计划vs完成（所有迭代）：[X/Y任务 = Z%]
趋势：[提升中 / 稳定 / 下降]
剩余工作调整后估算：[按当前速度所需天数]

Scope Recommendations

范围建议

Protect (Must ship with milestone)

保留项（必须随里程碑交付）

[Feature and why]

[功能及原因]

At Risk (May need to cut or simplify)

风险项（可能需要裁剪或简化）

[Feature and risk]

[功能及风险]

Cut Candidates (Can defer without compromising milestone)

候选裁剪项（可推迟且不影响里程碑核心价值）

[Feature and impact of cutting]

[功能及裁剪影响]

Go/No-Go Assessment

是否推进（Go/No-Go）评估

Recommendation: [GO / CONDITIONAL GO / NO-GO]

Conditions (if conditional):

[Condition 1 that must be met]
[Condition 2 that must be met]

Rationale: [Explanation of the recommendation]

建议：[GO / 有条件推进 / NO-GO]

条件（如果是有条件推进）：

[必须满足的条件1]
[必须满足的条件2]

理由：[建议的解释说明]

Action Items

行动项

#	Action	Owner	Deadline

---

#	行动	负责人	截止日期

---

Phase 3b: Producer Risk Assessment

阶段3b：负责人风险评估

Review mode check — apply before spawning PR-MILESTONE:

```
solo
```
→ skip. Note: "PR-MILESTONE skipped — Solo mode." Present the Go/No-Go section without a producer verdict.
```
lean
```
→ skip (not a PHASE-GATE). Note: "PR-MILESTONE skipped — Lean mode." Present the Go/No-Go section without a producer verdict.
```
full
```
→ spawn as normal.

Before generating the Go/No-Go recommendation, spawn

producer

via Task using gate PR-MILESTONE (

.claude/docs/director-gates.md

Pass: milestone name and target date, current completion percentage, blocked story count, velocity data from sprint reports (if available), list of cut candidates.

Present the producer's assessment inline within the Go/No-Go section. The producer's verdict (ON TRACK / AT RISK / OFF TRACK) informs the overall recommendation.

If OFF TRACK, use

AskUserQuestion

before generating the recommendation:

Prompt: "Producer verdict: OFF TRACK. The milestone is in jeopardy. This review will recommend NO-GO. How do you want to proceed?"

Options:

[A] Accept NO-GO — generate the full review with that recommendation

[B] Override to CONDITIONAL GO — I'll document the accepted risks myself

[C] Stop — I want to address blockers before generating the review

If AT RISK, use

AskUserQuestion

Prompt: "Producer verdict: AT RISK. Milestone may slip. How should the Go/No-Go section be framed?"

Options:

[A] CONDITIONAL GO — include producer's conditions in the review

[B] NO-GO — conditions cannot be met in time

[C] GO — I accept the risk and want to proceed

Do not issue a GO against an OFF TRACK verdict unless the user explicitly selects [B] above.

评审模式检查 — 在生成PR-MILESTONE前执行：

```
solo
```
→ 跳过。备注："PR-MILESTONE已跳过 — Solo模式。" 仅展示Go/No-Go部分，无需负责人结论。
```
lean
```
→ 跳过（非PHASE-GATE）。备注："PR-MILESTONE已跳过 — Lean模式。" 仅展示Go/No-Go部分，无需负责人结论。
```
full
```
→ 正常生成。

在生成Go/No-Go建议前，通过Task使用检查点PR-MILESTONE（

.claude/docs/director-gates.md

）调用

producer

。

传递参数：里程碑名称和目标日期、当前完成率、阻塞的故事数量、迭代报告中的速度数据（如有）、候选裁剪项列表。

在Go/No-Go部分内联展示负责人的评估结果。负责人的结论（ON TRACK / AT RISK / OFF TRACK）将作为整体建议的依据。

如果结论为OFF TRACK，在生成建议前使用

AskUserQuestion

：

提示："负责人结论：OFF TRACK。里程碑处于危险状态。本次评审将建议NO-GO。您希望如何处理？"

选项：

[A] 接受NO-GO — 生成包含该建议的完整评审报告

[B] 覆盖为有条件推进 — 我将自行记录已接受的风险

[C] 终止 — 我想先解决阻塞问题再生成评审报告

如果结论为AT RISK，使用

AskUserQuestion

：

提示："负责人结论：AT RISK。里程碑可能延期。Go/No-Go部分应如何表述？"

选项：

[A] 有条件推进 — 在评审报告中包含负责人提出的条件

```
[B] NO-GO — 无法及时满足条件
```

[C] GO — 我接受风险并希望继续推进

除非用户明确选择上述[B]选项，否则不得违背OFF TRACK结论给出GO建议。

Phase 4: Save Review

阶段4：保存评审报告

Present the review to the user.

Ask: "May I write this to

production/milestones/[milestone-name]-review.md

If yes, write the file, creating the directory if needed. Verdict: COMPLETE — milestone review saved.

If no, stop here. Verdict: BLOCKED — user declined write.

向用户展示评审报告。

询问："是否将此报告写入

production/milestones/[milestone-name]-review.md

？"

如果是，写入文件，必要时创建目录。结论：COMPLETE — 里程碑评审报告已保存。

如果否，在此终止。结论：BLOCKED — 用户拒绝写入。

Phase 5: Next Steps

阶段5：后续步骤

Run
```
/gate-check
```
for a formal phase gate verdict if this milestone marks a development phase boundary.
Run
```
/sprint-plan
```
to adjust the next sprint based on the scope recommendations above.

如果此里程碑标志着开发阶段的边界，运行
```
/gate-check
```
以获取正式的阶段检查点结论。
运行
```
/sprint-plan
```
，根据上述范围建议调整下一个迭代计划。