agile-review

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Sprint Review

Sprint评审

Use this skill to consolidate sprint deliveries into a clear, objective review/demo format for stakeholders.

使用本Skill将Sprint交付成果整理为面向利益相关者的清晰、客观的评审/演示格式。

Language

语言要求

Write the artifact in the user's language. Apply correct grammar and any required diacritics or script-specific characters. If the user's language is unclear, ask before generating output. Templates are in English — translate headers and content to match.

以用户使用的语言撰写文档。确保语法正确，并使用所需的变音符号或特定脚本字符。若用户使用的语言不明确，在生成输出前先询问用户。模板为英文版本，请将标题和内容翻译为对应语言。

Project root

项目根目录

This skill writes artifacts at paths relative to the project root (the repo where the work happens), not the agent's current working directory.

If invoked from inside the project, use the relative paths shown in this skill.
If invoked from another directory (e.g., a sibling repo, or when the project lives elsewhere), prepend
```
<project-root>/
```
to every artifact path.
When the project root is ambiguous, confirm with the user via the harness question tool before writing.

本Skill会将文档写入相对于项目根目录（即开展工作的代码仓库）的路径下，而非Agent当前的工作目录。

若在项目内部调用，使用本Skill中所示的相对路径。
若从其他目录调用（例如同级代码仓库，或项目位于其他位置），请在每个文档路径前添加
```
<project-root>/
```
。
若项目根目录不明确，在写入前通过工具的提问功能与用户确认。

Prompting

提示规则

Follow the project-wide convention in

CLAUDE.md

AGENTS.md

("Skill Prompting Conventions"). Use the harness's structured-question tool —

AskUserQuestion

(Claude Code),

ask_user_question

(Codex), or

question

(OpenCode) — for the decision points below. Use free-form text only where a path/name/value cannot be enumerated.

Decision point	Why structured	Suggested options
Audience	Shapes the demo content	Team-only · Stakeholders · Mixed
Demo scope	Branches the artifact	Done items only · Include in-progress

Free-form prompts (no structured tool):

Stakeholder names
Demo narration text

No-pause mode: if the user has explicitly disabled mid-skill clarification, convert every structured prompt into an entry under Open questions (or equivalent) and proceed without blocking.

遵循

CLAUDE.md

AGENTS.md

中的项目级约定（「Skill提示规则」）。针对以下决策点，使用工具的结构化提问功能——

AskUserQuestion

（Claude Code）、

ask_user_question

（Codex）或

question

（OpenCode）。仅当路径/名称/值无法枚举时，才使用自由格式文本。

决策点	使用结构化提问的原因	建议选项
受众	影响演示内容	仅团队 · 利益相关者 · 混合
演示范围	决定文档分支	仅已完成项 · 包含进行中项

自由格式提示（不使用结构化工具）：

利益相关者姓名
演示旁白文本

无暂停模式：若用户明确禁用Skill执行过程中的澄清环节，请将所有结构化提示转换为「开放式问题」（或同类板块）下的条目，无需等待即可继续执行。

Objective

目标

Consolidate what was delivered in the sprint
Compare deliveries against sprint planning commitment
Highlight scope changes, deviations, and decisions made
Prepare objective demonstration of delivered value
Collect stakeholder feedback to feed the next cycle

整理Sprint期间的所有交付成果
将交付成果与Sprint计划承诺进行对比
突出范围变更、偏差及已做出的决策
准备对交付价值的客观演示
收集利益相关者反馈，为下一周期提供输入

When to use

使用场景

At the end of a sprint, before retro
When stakeholders need to see the result of deliveries
When it is necessary to validate that the product is on the right track
To close the cycle between sprint planning and retrospective

Sprint结束后，回顾会议之前
利益相关者需要查看交付成果时
需要验证产品是否处于正确发展轨道时
完成从Sprint计划到回顾会议的闭环

Process

流程

1. Consolidate deliveries

1. 整理交付成果

Gather information from:

Issues completed in the sprint
Status closure reports generated
Status checkpoints and consolidation reports from the period
Registered scope changes

For each delivered item, register:

What was expected (from sprint planning)
What was actually delivered
Relevant deviations (if any)

从以下渠道收集信息：

Sprint期间完成的议题
生成的状态关闭报告
该期间的状态检查点和整理报告
已记录的范围变更

针对每个已交付项，记录：

预期内容（来自Sprint计划）
实际交付内容
相关偏差（如有）

2. Prepare demonstration

2. 准备演示内容

Organize the demo by business value, not technical order:

Start with impact: "now the team can do X"
Show the flow working, not slides
If there is relevant technical part (performance, security), include as context

按照业务价值而非技术顺序组织演示：

从影响入手：「现在团队可以完成X事项」
展示实际运行流程，而非仅用幻灯片
若涉及相关技术部分（性能、安全），将其作为背景信息纳入

3. Identify undelivered items

3. 识别未交付项

For each planned item that was not delivered:

Reason: blocker, priority change, scope larger than expected
Destination: returns to backlog, enters next sprint, was discarded

针对每个未交付的计划项：

原因：阻塞问题、优先级变更、范围超出预期
去向：返回待办清单、进入下一Sprint、已废弃

4. Collect feedback

4. 收集反馈

Necessary adjustments
New needs identified
Priority changes

记录利益相关者的问题和反馈：

必要的调整
识别出的新需求
优先级变更

5. Generate artifact

5. 生成文档

Use the template below to document the review.

使用以下模板记录评审内容。

Template

模板

Use

templates/review.md

from this skill as base for the artifact.

以本Skill中的

templates/review.md

作为文档基础。

Rules

规则

The review shows what was delivered, not what is in progress. For status of work in progress, use
```
/agile-status
```
.
Be honest about what was not delivered and why. Hiding cut items breaks trust.
The demo must be verifiable — stakeholders must be able to confirm the result is real.
Collected feedback must become backlog item or action, never just meeting notes.
The sprint review feeds the retro. If the review doesn't happen, the retro loses important inputs.

评审内容应展示已交付成果，而非进行中工作。如需跟踪进行中工作的状态，请使用
```
/agile-status
```
。
如实说明未交付内容及原因。隐瞒取消的事项会破坏信任。
演示必须可验证——利益相关者必须能够确认成果真实有效。
收集到的反馈必须转化为待办清单项或行动，不能仅作为会议记录。
Sprint评审为回顾会议提供输入。若未开展评审，回顾会议将失去重要信息来源。

Relationship with the flow

与流程的关联

mermaid

flowchart LR
    A["/agile-sprint"] --> B[execution]
    B --> C["/agile-status"]
    C --> D["/agile-metrics"]
    D --> E["/agile-review"]
    E --> F["/agile-retro"]

In the stitched flow, the sprint review connects execution to feedback: planning -> execution -> status -> metrics -> review -> retro.

For status tracking during the sprint, use

/agile-status

. For quantitative data, use

/agile-metrics

mermaid

flowchart LR
    A["/agile-sprint"] --> B[execution]
    B --> C["/agile-status"]
    C --> D["/agile-metrics"]
    D --> E["/agile-review"]
    E --> F["/agile-retro"]

在串联流程中，Sprint评审将执行环节与反馈环节相连：计划 → 执行 → 状态 → 指标 → 评审 → 回顾。

Sprint期间的状态跟踪，请使用

/agile-status

。如需获取量化数据，请使用

/agile-metrics

。