Plan Sprint

Collaboratively select milestones for a sprint with the user.

Arguments

$ARGUMENTS - Sprint identifier (e.g., "2025-W01") or empty for next sprint

Instructions

1. Determine the sprint:

   • If $ARGUMENTS provided, use that sprint (format: YYYY-WNN)
   • If empty, calculate next sprint from today's date

2. Calculate sprint dates:

   • Start: Monday of week NN
   • End: Friday of week NN+1 (2 weeks)

3. Ask about availability:

   Sprint 2025-W01 (Jan 6-17)
   
   Team availability:
   - Alice: Any PTO or reduced capacity? [default: 10 days]
   - Bob: Any PTO or reduced capacity? [default: 10 days]
   

4. Calculate capacity:

   Team Capacity:
   | Dev | Days | Capacity |
   |-----|------|----------|
   | Alice | 10 | 20 pts |
   | Bob | 8 | 16 pts |
   | Total | - | 36 pts |
   
   Buffer (15%): 5 pts
   Available: 31 pts
   

5. Show available milestones:

   Available milestones (planned, not committed):
   
   | Epic | Milestone | Points |
   |------|-----------|--------|
   | User Auth | M1: Auth foundation | 8 |
   | User Auth | M2: OAuth providers | 13 |
   | Dashboard | M1: Chart components | 10 |
   
   Which milestones for this sprint?
   

6. Track commitment:

   Selected: M1 Auth foundation (8 pts)
   
   Committed: 8 / 31 pts (26%)
   Remaining: 23 pts
   
   Add more? [Y/n]
   

7. Warn if over capacity:

   ⚠️ At 95% capacity (30/31 pts)
   Consider leaving buffer for unexpected work.
   
   Proceed anyway? [Y/n]
   

8. Create sprint file:

   • Save to .roadmap/sprints/2025-W01.md
   • Update epic files with sprint assignments

9. Next steps:

   Sprint 2025-W01 planned with 3 milestones (28 pts).
   
   Next:
   - /roadmap-planner:status sprint    - Track progress
   - /clickup-sync:push                - Sync to ClickUp