Sprint Plan
- 1.9k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
sprint-plan produces capacity-based sprint plans with goals, stories, and risks.
About
The sprint-plan skill helps teams plan a sprint by estimating capacity from team availability and historical velocity, selecting backlog stories against Definition of Ready, mapping dependencies and critical path, and identifying risks with mitigations. Capacity calculation reserves fifteen to twenty percent buffer for bugs, on-call, and unexpected work. Story selection pulls highest priority items, flags items needing refinement, and stops when capacity is reached. Output summary includes sprint goal sentence, duration, team capacity in points, committed stories, buffer remaining, ordered story list with owners and dependencies, and risk mitigations. Agents read user backlogs, velocity data, and prior sprint reports when provided. Use when preparing sprint planning, balancing scope against velocity, or defining the sprint goal. Estimates capacity from availability, velocity, and 15-20% buffer. Selects stories meeting Definition of Ready until capacity fills.
- Estimates capacity from availability, velocity, and 15-20% buffer.
- Selects stories meeting Definition of Ready until capacity fills.
- Maps dependencies, critical path, and external blockers.
- Identifies risks with mitigations per story.
- Outputs sprint goal, committed stories, and capacity summary.
Sprint Plan by the numbers
- 1,887 all-time installs (skills.sh)
- +92 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #264 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
sprint-plan capabilities & compatibility
- Capabilities
- capacity estimation · story selection · dependency mapping · risk identification
- Use cases
- planning · project management
What sprint-plan says it does
Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.
Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
npx skills add https://github.com/phuryn/pm-skills --skill sprint-planAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.9k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
What stories fit this sprint given team capacity and dependencies?
Plan sprints with capacity estimation, story selection, dependency mapping, risks, and a single clear sprint goal.
Who is it for?
Scrum teams running sprint planning ceremonies.
Skip if: Quarterly roadmap strategy or annual capacity modeling.
When should I use this skill?
User prepares sprint planning, estimates capacity, or selects sprint stories.
What you get
Sprint plan with goal, committed points, story list, and risk mitigations.
- Sprint capacity sheet
- Selected story list
- Risk and dependency notes
Files
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
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
How much capacity should be reserved as buffer?
Fifteen to twenty percent for unexpected work, bugs, and tech debt.
When should story selection stop?
When committed points reach available team capacity.
What defines a ready story?
Clear acceptance criteria, estimate present, and no blockers per Definition of Ready.
Is Sprint Plan safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.