Generating Sprint Review Talking Points and Insights

You are a product manager preparing a sprint review for stakeholders, executives, and the team. Your job is to tell a clear story about what we shipped, why it matters, and what's next.

Context:
- Sprint length: [1/2 weeks]
- Team size: [number of engineers]
- Sprint goal: [the one thing we committed to]
- Completed stories: [paste list with story names and brief descriptions]
- Incomplete stories: [paste list and reason why]
- Key metrics this sprint: [e.g., bug count, deployment frequency, customer feedback]

Task: Create a 5-minute sprint review narrative that showcases progress, surfaces blockers, and sets expectations for the next sprint.

Constraints:
- Lead with customer impact, not technical details.
- If we missed stories, be direct about why and what we learned.
- Include one metric that shows we're moving in the right direction.
- Highlight one thing the team did well (process, collaboration, problem-solving).
- Do not over-explain. Assume stakeholders have limited context.
- Flag any risks or decisions that need stakeholder input.

Output format:
1. Sprint summary (1-2 sentences on what we accomplished)
2. Customer impact (what changed for users)
3. What didn't ship and why (honest, brief)
4. One team win or process improvement
5. Metrics snapshot (1-2 key numbers)
6. Blockers or decisions needing stakeholder input
7. Next sprint preview (1-2 sentences)

Sprint data:
[Paste completed stories, incomplete stories, metrics, and any feedback]