sprint-plan · git:20260303.a372bee · 2026-03-03 · sha256 54ac27165fd7d57f
sprint-plan git:20260303.a372beeA
Immutable. This exact content never changes and is served at /api/v1/blob/54ac27165fd7d57f.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_55ks2hizhccc4s5r/54ac27165fd7d57fe3f598f1ef66087d03fbf56d9f583adf7608ccaca9ce3382.json
Then /plugin install sprint-plan@markdownregistry-55ks2hizhccc4s5r in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: sprint-plan description: "Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity." --- ## Sprint Planning Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks. ### Context You are helping plan a sprint for **$ARGUMENTS**. If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first. ### Instructions 1. **Estimate team capacity**: - Number of team members and their availability (PTO, meetings, on-call) - Historical velocity (average story points per sprint from last 3 sprints) - Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt - Calculate available capacity in story points or ideal hours 2. **Review and select stories**: - Pull from the prioritized backlog (highest priority first) - Verify each story meets the Definition of Ready (clear AC, estimated, no blockers) - Flag stories that need refinement before committing - Stop adding stories when capacity is reached 3. **Map dependencies**: - Identify stories that depend on other stories or external teams - Sequence dependent stories appropriately - Flag external dependencies and owners - Identify the critical path 4. **Identify risks and mitigations**: - Stories with high uncertainty or complexity - External dependencies that could slip - Knowledge concentration (only one person can do it) - Suggest mitigations for each risk 5. **Create the sprint plan summary**: ``` Sprint Goal: [One sentence describing what success looks like] Duration: [2 weeks / 1 week / etc.] Team Capacity: [X story points] Committed Stories: [Y story points across Z stories] Buffer: [remaining capacity] Stories: 1. [Story title] — [points] — [owner] — [dependencies] ... Risks: - [Risk] → [Mitigation] ``` 6. **Define the sprint goal**: A single, clear sentence that captures the sprint's primary value delivery. Think step by step. Save as markdown. --- ### Further Reading - [Product Owner vs Product Manager: What's the difference?](https://www.productcompass.pm/p/product-manager-vs-product-owner)