sprint-review

Conduct Scrum Sprint Reviews and preserve remaining work as draft PBIs.

15|5|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sohei56/maul-team --skill sprint-review-sohei56
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-review
Source: https://github.com/sohei56/maul-team/tree/main/skills/sprint-review
Command: npx skills add https://github.com/sohei56/maul-team --skill sprint-review-sohei56

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill runs a disciplined Sprint Review that turns completed work, incomplete items, documentation gaps, and stakeholder feedback into an auditable product backlog without losing follow-up work.

Core Features & Use Cases

  • Increment Review: Summarize the Sprint Goal, completed PBIs, incomplete PBIs, and Product Goal progress.
  • Acceptance and Quality Checks: Launch and demonstrate the application, verify every completed PBI, and compare implementation against product documentation.
  • Backlog Continuity: Materialize carry-overs, defects, changes, feedback, and documentation mismatches as draft PBIs while preserving the original Sprint history.
  • Use Case: After a development Sprint, use this Skill to present the working Increment, collect acceptance decisions and feedback, append the Sprint Summary, report all leftover work, and commit the Sprint deliverables.

Quick Start

Use the sprint-review skill when the Scrum state is in the review phase to conduct the complete Sprint Review and commit its deliverables.

Frequently Asked Questions about sprint-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a Sprint Review that captures stakeholder feedback and backlog carry-overs?

A Sprint Review validates completed work, demonstrates the Increment, triages feedback, and converts carry-overs into draft PBIs. This preserves all remaining product work in the backlog while maintaining auditable Sprint history.

What is the best way to track incomplete Product Backlog Items after a Sprint ends?

Track incomplete Product Backlog Items by materializing them as draft PBIs during the Sprint Review. This process safely preserves the original Sprint history while ensuring carry-over work is documented for future Sprints.

How do I verify completed PBIs against product documentation during a Sprint Review?

Verifying completed PBIs involves launching the application, demonstrating the working Increment, and comparing the implementation against product documentation to identify any mismatches or gaps requiring follow-up work.

Do I need specific Scrum state records to run a structured Sprint Review?

Yes, running a Sprint Review requires Sprint state, Sprint records, and the product backlog. It also relies on the repository's Scrum state-management wrappers to safely update ceremony status, history, and draft PBIs.

Why does stakeholder feedback need to be triaged during the Sprint Review?

Stakeholder feedback is triaged during the Sprint Review to turn acceptance decisions, defects, and documentation gaps into an auditable product backlog. This ensures all input is captured as actionable draft PBIs without losing follow-up work.

Can I update Sprint history and ceremony status without losing original backlog data?

Yes, the Sprint Review process safely updates ceremony status and history using Scrum state-management wrappers. It materializes carry-overs and feedback as draft PBIs, preserving original Sprint history without losing backlog data.