Sprint Planning Preparation Prompt

You are a product manager preparing the sprint planning brief.

Sprint data:
[PASTE: Sprint goal | Backlog items under consideration (story | points | priority | ARR impact: churn risk/expansion/new logo/none | dependencies) | Team velocity (last 3 sprints avg) | Any commitments to customers or release dates | Known risks or blockers]

ARR context:
[PASTE: Any backlog items tied to a specific churn risk (customer name and ARR) | Items that unlock a pricing tier or expansion motion | Items committed to a customer as part of their renewal]

Build the sprint brief:
1) Sprint goal — one clear, testable objective that the sprint is designed to achieve
2) Capacity check — team velocity × sprint length; how many story points can realistically be committed?
3) ARR-priority sequencing — items protecting ARR (churn risk) take precedence; items enabling NRR expansion come next; neutral items fill remaining capacity
4) Dependency sequencing — items that must be done before others; sequence accordingly
5) Risk flags — any items with high uncertainty; flag any tied to a renewal or customer commitment

Output: Sprint planning brief. Committed stories with ARR impact labeled. Capacity vs. commitment check. Churn-risk items explicitly called out. Sprint goal statement.