Sprint Plan
Added March 10, 2026 Source: Pawel Huryn
Plan out an entire sprint from start to finish. It helps you estimate team capacity, select stories, map dependencies, and identify potential risks for a successful sprint.
Installation
This skill is self-contained. Copy the SKILL.md below directly into your project to get started.
.claude/skills/sprint-plan/SKILL.md # Claude Code
.cursor/skills/sprint-plan/SKILL.md # CursorOr install as a personal skill (available across all your projects):
~/.claude/skills/sprint-plan/SKILL.mdYou can also install using the skills CLI:
npx skills add phuryn/pm-skills --skill sprint-planRequires Node.js 18+.
SKILL.md
---
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)
Originally by Pawel Huryn, adapted here as an Agent Skills compatible SKILL.md.
This skill follows the Agent Skills open standard, supported by Claude Code, Cursor, Codex, Gemini CLI, and 20+ more editors.
Works with
Agent Skills format — supported by 20+ editors. Learn more