
Sprint Planning Assistant
Build realistic sprint scopes by analyzing backlog, estimating complexity, and mapping dependencies.
What You Can Do
This skill helps you construct realistic sprint scopes by analyzing backlog items against your team's historical velocity and capacity. You provide your prioritized backlog, team velocity data, and upcoming sprint capacity—Claude reviews each item for complexity, maps interdependencies, surfaces risks, and proposes a recommended sprint scope with confidence intervals. You get an explicit, data-informed sprint plan that improves team confidence and delivery predictability.
Features
Reviews prioritized items and identifies refinement gaps or ambiguities
Assigns story point ranges or t-shirt sizes based on scope and risk
Surfaces cross-story and cross-team dependencies that affect sequencing
Flags technical, capacity, and external risks that could derail sprint delivery
Calibrates recommended scope against 2+ sprints of historical velocity data
Generates multiple scenarios (conservative, realistic, aggressive) with confidence estimates
Accounts for team size changes, planned absences, and non-sprint work
Example Output
Backlog Analysis Summary
- 18 items in backlog; 3 items lack clear acceptance criteria
- High-priority items: API refactor (8 pts), Auth redesign (5 pts), Reporting dashboard (8 pts)
Dependency Map
- Auth redesign blocks Dashboard (cross-team handoff)
- API refactor blocks 4 downstream items
- Mobile team dependency on API refactor (2-day async lag expected)
Risk Callouts
- 🚨 High: API refactor scope creep (design not finalized)
- ⚠️ Medium: Auth team capacity uncertainty (1 person on leave)
- ⚠️ Medium: Third-party payment API integration (external vendor)
Sprint Proposals
| Scenario | Items | Points | Confidence | Notes |
|---|---|---|---|---|
| Conservative | 6 | 28 | 95% | Protects against scope creep |
| Realistic | 8 | 34 | 75% | Aligns with 3-sprint velocity |
| Aggressive | 10 | 42 | 50% | Only if API refactor stays on track |
What's Included
- SKILL.md: Complete Sprint Planning Assistant instruction file
- Backlog Template: Markdown table format for prioritized items with story point ranges
- Velocity Tracker: Simple spreadsheet format to calculate and monitor team velocity
- Dependency Mapping Checklist: Guided checklist for identifying cross-item and cross-team dependencies
- Risk Register Template: Structured format for logging and scoring identified risks
- Sprint Proposal Framework: Multi-scenario output template (Conservative/Realistic/Aggressive)
Who It's For
- Scrum Masters & Agile Coaches — Need structured facilitation input for sprint planning sessions
- Engineering Managers — Want defensible sprint commitments backed by data and risk analysis
- Tech Leads — Balance team capacity against dependency complexity and technical risk
- Product Managers — Need realistic timelines for prioritized features and cross-team handoffs
- Program Managers — Coordinate multi-team sprints with complex interdependencies
Best For
- Sprint planning preparation — Transform raw backlog into structured input 1-3 days before meeting
- Capacity re-planning — Recalibrate scope when team size, velocity, or priorities shift mid-cycle
- Dependency complexity — Map and sequence items when multiple teams or technical blockers exist
- Risk-sensitive planning — Surface unknowns and confidence gaps when delivery predictability is critical
- Velocity calibration — Validate historical velocity assumptions and adjust for team changes







