What problem does it solve? Teams often end a Sprint without a structured way to show stakeholders what was actually finished, so feedback gets lost in meeting notes and the Product Backlog never reflects what was learned. This Skill operationalizes the Scrum Sprint Review ceremony: it enforces that only work meeting the Definition of Done is demonstrated, converts stakeholder feedback into concrete backlog items, and leaves the Product Backlog re-prioritized for the next Sprint Planning. ## Core Features & Use Cases - Structured ceremony flow: Guides the five moments of a Sprint Review — framing the Sprint Goal, reporting backlog status, demonstrating the Increment live, collecting stakeholder feedback, and re-prioritizing the backlog. - Feedback-to-backlog conversion: Provides a capture template (description, origin, value, priority, traceability) so every relevant stakeholder comment becomes a Product Backlog item instead of a lost note. - Quality gates and anti-patterns: Enforces four quality gates (only Done work shown, feedback captured as items, real stakeholders present, backlog updated) and lists common failure modes like demoing unfinished work or turning the Review into a Retrospective. - Use Case: At the end of a two-week Sprint on an e-commerce checkout feature, use this Skill to demo the Done increment to the business sponsor, record their request to show shipping costs earlier as a new backlog item, and re-prioritize the backlog before Sprint Planning. ## Quick Start Run the scrum-sprint-review skill to close this Sprint by demonstrating the Done increment to stakeholders and updating the Product Backlog with their feedback.
