---
name: minimalist-sprint-review
description: Use when a sprint increment is ready to demonstrate and each selected story needs an acceptance decision, user feedback, and a traceable follow-up.
---

# Minimalist Sprint Review

Resolve review.md from <plugin-root>/templates/ and the feedback
classification from <plugin-root>/references/artifact-contracts.md.

Inspect the working increment with the decision-maker before starting the next
selection. The review evaluates the selected stories against their criteria; it
does not expand the sprint retroactively.

## Prepare

Read the Sprint Goal, selected story IDs, acceptance criteria, Definition of
Done, verification evidence, and any carry-over notes. Demonstrate the smallest
working behavior that proves the goal. Report failures and limitations plainly.

## Produce

Create feedback/###-review.md and update each selected story with:

- what was demonstrated;
- acceptance decision;
- user observations;
- feedback classification;
- next action and target iteration.

Use one classification per request:

- acceptance;
- change-request;
- defect;
- new-need;
- rejected;
- carried-over.

A story may be demonstrated without being accepted. Record the difference.

## Backlog updates

Convert feedback into explicit records:

- acceptance closes the current story;
- a change request updates the criteria or creates a successor story;
- a defect links to the selected story;
- a new need creates a new backlog story;
- rejection records the reason;
- incomplete work returns as carried-over with remaining scope.

Preserve the original story, sprint plan, criteria, evidence, and decision. Do not
rewrite history to make the increment appear more complete.

## Gate

Review is complete only when every selected story has a demonstration result,
decision, classification, feedback record, and next action. The updated backlog
must reflect every new, changed, defective, rejected, or carried-over item.

## Handoff

Pass the review record and updated story/backlog records to
minimalist-sprint-retrospective. Do not select the next sprint before feedback is
classified and recorded.