| name | sprint-review |
| description | Facilitate a Scrum Sprint Review event, capturing what was built, stakeholder feedback from the demo, and decisions about the path forward. Invoke when the sprint has concluded and the team is ready to present its increment to stakeholders. |
Adapted from bmad-method:bmad-sprint-status (MIT, © 2025 BMad Code, LLC). See THIRD_PARTY_NOTICES.md.
When to use
Use this skill at the conclusion of a sprint, after the sprint work is done and before the retrospective begins. Typical triggers include:
- The sprint timebox has ended and the team is preparing to demo the increment to stakeholders.
- The Product Owner needs a structured record of what was completed versus what was not, and why.
- The team wants to capture stakeholder feedback systematically so it can inform the next sprint's backlog prioritization.
Do not invoke for mid-sprint status checks, retrospective facilitation, or sprint planning; those are separate skills with distinct purposes.
Summon the SME
Before facilitating, load the Scrum Guide reference on the Sprint Review to ground the session in established Scrum practice.
Reading the config. Check .pm-kit.config.json for the sourcesMode field:
- If
sourcesMode is "online" (opt-in): fetch the URL stored at the key sources.scrumGuide in vendor/pm-kit/sources-index.json using your available web-fetch capability. Do not name a specific tool — use whatever your runtime provides. Navigate to the Sprint Review section. Do not fabricate quotations or page numbers.
- If
sourcesMode is "offline" or the field is absent (the default): rely on your general knowledge of the Sprint Review as defined in the 2020 Scrum Guide — a working session in which the Scrum Team and stakeholders inspect the sprint outcome and determine future adaptations. Cite the canonical URL from vendor/pm-kit/sources-index.json at key sources.scrumGuide in the output. Do not fabricate quotations or page numbers.
In both cases, the URL to cite is https://scrumguides.org/scrum-guide.html.
Facilitation script
Walk the user through these steps in sequence. Do not skip steps or combine them.
Step 1 — Gather inputs. Ask the user to provide: (a) the sprint number and dates, (b) the list of attendees including all stakeholder names and roles, and (c) the Sprint Backlog as committed at planning.
Step 2 — Sprint goal review. Ask: "Was the sprint goal met?" Guide the user to answer with one of: fully met, partially met, or not met. If partially or not met, ask what prevented full achievement. Record a brief, factual narrative.
Step 3 — Completed work. For each story in the Sprint Backlog, ask: "Was this story completed and accepted?" Record each story's status and whether its acceptance criteria were fully met. This becomes the "Completed work" section of the artifact.
Step 4 — Incomplete work. For each story that was not completed or not accepted, ask: "What prevented completion?" and "What is the plan for this item?" Record the reason and the intended disposition: return to backlog, carry forward into the next sprint, or deprecate.
Step 5 — Demo and stakeholder feedback. Guide the user through capturing feedback from the demo. For each piece of feedback, ask: "What was said, and by whom?" Group feedback by theme after collection. Aim for verbatim capture where possible — paraphrasing loses signal.
Step 6 — Decisions. Ask: "What scope or priority changes were agreed to during this meeting?" Record each decision with the person who approved it.
Step 7 — Next sprint hints. Ask: "Based on today's review and feedback, what are the strongest signals for next sprint's backlog?" Record two to four hints — these are not commitments, just directional inputs for the next planning session.
Step 8 — Produce the artifact. Assemble the completed Sprint Review document using the structure in TEMPLATE.md (sibling file). Fill every section. Leave no placeholder unfilled.
Step 9 — Save the artifact. Save the filled artifact to docs/pm-kit/outputs/sprint-review/<short-slug>.md. <short-slug> is a kebab-case ASCII slug (max 40 chars) derived from the sprint number (e.g., sprint-03-review). Confirm the final path with the user before writing. If the file exists, ask: overwrite, append a date suffix (e.g., -2026-04-20), or pick a new slug. The artifact begins with the three-line provenance header below (HTML comments, do not render):
<!-- Generated by agentic-pm-kit:sprint-review on YYYY-MM-DD -->
<!-- Languages: communication=<value>, output=<value> -->
<!-- Source mode: offline | online -->
Languages
The kit separates the language used for live agent–user dialogue from the language used in the saved artifact. Both values live in .pm-kit.config.json and are free-form strings — read each value verbatim, never infer a language from the conversation, and never select from a hardcoded list.
Facilitation dialogue. Speak to the user during facilitation in the language at language.communication. Use the string verbatim.
Filled artifact (saved TEMPLATE.md output). Produce the written artifact in the language at language.output. If language.output is absent or empty, fall back to language.communication.
Example values either field might contain: "en-US", "es-MX", "Português brasileiro", "Mandarin Chinese". Accept any string as given.
Acceptance gate
When the Sprint Review record is complete, point the user to CHECKLIST.md (sibling file) and ask them to verify each item. Remind them that the output must be marked PASS or FAIL. On FAIL, invite the user to return with specific notes so the facilitation can be resumed or corrected.
