sprint-plan

1## Sprint Planning
2 
3Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.
4 
5### Context
6 
7You are helping plan a sprint for **$ARGUMENTS**.
8 
9If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.
10 
11### Instructions
12 
131. **Estimate team capacity**:
14   - Number of team members and their availability (PTO, meetings, on-call)
15   - Historical velocity (average story points per sprint from last 3 sprints)
16   - Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
17   - Calculate available capacity in story points or ideal hours
18 
192. **Review and select stories**:
20   - Pull from the prioritized backlog (highest priority first)
21   - Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
22   - Flag stories that need refinement before committing
23   - Stop adding stories when capacity is reached
24 
253. **Map dependencies**:
26   - Identify stories that depend on other stories or external teams
27   - Sequence dependent stories appropriately
28   - Flag external dependencies and owners
29   - Identify the critical path
30 
314. **Identify risks and mitigations**:
32   - Stories with high uncertainty or complexity
33   - External dependencies that could slip
34   - Knowledge concentration (only one person can do it)
35   - Suggest mitigations for each risk
36 
375. **Create the sprint plan summary**:
38 
39   ```
40   Sprint Goal: [One sentence describing what success looks like]
41…