Sprint Planning

1---2name: sprint-planning3description: Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.4argument-hint: "[sprint name or date range]"5---6 7# /sprint-planning8 9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).10 11Plan a sprint by scoping work, estimating capacity, and setting clear goals.12 13## Usage14 15```16/sprint-planning $ARGUMENTS17```18 19## How It Works20 21```22┌─────────────────────────────────────────────────────────────────┐23│                    SPRINT PLANNING                                 │24├─────────────────────────────────────────────────────────────────┤25│  STANDALONE (always works)                                       │26│  ✓ Define sprint goals and success criteria                     │27│  ✓ Estimate team capacity (accounting for PTO, meetings)        │28│  ✓ Scope and prioritize backlog items                           │29│  ✓ Identify dependencies and risks                              │30│  ✓ Generate sprint plan document                                │31├─────────────────────────────────────────────────────────────────┤32│  SUPERCHARGED (when you connect your tools)                      │33│  + Project tracker: Pull backlog, create sprint, assign items   │34│  + Calendar: Account for PTO and meetings in capacity           │35│  + Chat: Share sprint plan with the team                        │36└─────────────────────────────────────────────────────────────────┘37```38 39## What I Need From You40 41- **Team**: Who's on the team and their availability this sprint?42- **Sprint length**: How many days/weeks?43- **Backlog**: What's prioritized? (Pull from tracker, paste, or describe)44- **Carryover**: Anything unfinished from last sprint?45- **Dependencies**: Anything blocked on other teams?46 47## Output48 49```markdown50## Sprint Plan: [Sprint Name]51**Dates:** [Start] — [End] | **Team:** [X] engineers52**Sprint Goal:** [One clear sentence about what success looks like]53 54### Capacity55| Person | Available Days | Allocation | Notes |56|--------|---------------|------------|-------|57| [Name] | [X] of [Y] | [X] points/hours | [PTO, on-call, etc.] |58| **Total** | **[X]** | **[X] points** | |59 60### Sprint Backlog61| Priority | Item | Estimate | Owner | Dependencies |62|----------|------|----------|-------|--------------|63| P0 | [Must ship] | [X] pts | [Person] | [None / Blocked by X] |64| P1 | [Should ship] | [X] pts | [Person] | [None] |65| P2 | [Stretch] | [X] pts | [Person] | [None] |66 67### Planned Capacity: [X] points | Sprint Load: [X] points ([X]% of capacity)68 69### Risks70| Risk | Impact | Mitigation |71|------|--------|------------|72| [Risk] | [What happens] | [What to do] |73 74### Definition of Done75- [ ] Code reviewed and merged76- [ ] Tests passing77- [ ] Documentation updated (if applicable)78- [ ] Product sign-off79 80### Key Dates81| Date | Event |82|------|-------|83| [Date] | Sprint start |84| [Date] | Mid-sprint check-in |85| [Date] | Sprint end / Demo |86| [Date] | Retro |87```88 89## Tips90 911. **Leave buffer** — Plan to 70-80% capacity. You will get interrupts.922. **One clear sprint goal** — If you can't state it in one sentence, the sprint is unfocused.933. **Identify stretch items** — Know what to cut if things take longer than expected.944. **Carry over honestly** — If something didn't ship, understand why before re-committing.