Back to Details

agile-review

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sprint Review

Sprint Review

Use this skill to consolidate sprint deliveries into a clear, objective review/demo format for stakeholders.
使用本Skill将迭代交付成果整理为清晰、客观的评审/演示格式，呈现给利益相关者。

Language

语言要求

Write the artifact in the user's language. If the user communicates in Portuguese, write in Portuguese with correct grammar and accents. If in English, write in English. When in doubt, ask the user which language to use. Templates are in English — translate headers and content to match.
以用户使用的语言撰写文档。若用户使用葡萄牙语，则用葡萄牙语撰写，确保语法正确、带有正确重音；若使用英语，则用英语撰写。如有疑问，请询问用户使用何种语言。模板为英文版本，请将标题和内容翻译为对应语言。

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
  • 整合迭代期间的交付成果
  • 对比交付成果与迭代规划承诺
  • 突出范围变更、偏差及已做出的决策
  • 准备对交付价值的客观演示
  • 收集利益相关者反馈，为下一周期提供输入

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
  • 迭代结束后，回顾会议（Retro）之前
  • 利益相关者需要查看交付成果时
  • 需要验证产品是否处于正确轨道时
  • 完成从迭代规划到回顾会议的周期闭环时

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)
从以下渠道收集信息：
  • 迭代内完成的任务（Issues）
  • 生成的状态关闭报告
  • 周期内的状态检查点与整合报告
  • 已记录的范围变更
针对每个交付项，记录：
  • 预期内容（来自迭代规划）
  • 实际交付内容
  • 相关偏差（如有）

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
针对每个未交付的规划项：
  • 原因：阻塞问题、优先级变更、范围超出预期
  • 去向：退回待办事项（Backlog）、进入下一个迭代、已被废弃

4. Collect feedback

4. 收集反馈

Register stakeholder questions and feedback:
  • Necessary adjustments
  • New needs identified
  • Priority changes
记录利益相关者的问题与反馈：
  • 必要的调整
  • 识别出的新需求
  • 优先级变更

5. Generate artifact

5. 生成文档

Use the template below to document the review.
使用以下模板记录评审内容。

Template

模板

Use 
~/.agents/templates/review.md
as base for the artifact.
以
~/.agents/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评审连接了执行环节与反馈环节：规划 -> 执行 -> 状态 -> 指标 -> 评审 -> 回顾。
如需在迭代期间跟踪状态，请使用
/agile-status
；如需获取量化数据，请使用
/agile-metrics
。