sprint-plan
phuryn/pm-skills
Plan sprints with capacity estimation, story selection, dependency mapping, and risk identification.
What is sprint-plan?
Sprint Planning helps you prepare for sprint planning by estimating team capacity, selecting and sequencing stories from the backlog, mapping dependencies, and identifying risks. Use it when preparing sprints, balancing scope against velocity, or estimating what your team can realistically commit to.
- Estimate team capacity based on availability, historical velocity, and buffers for unexpected work
- Review and select stories from the prioritized backlog, flagging those needing refinement
- Map story dependencies and identify the critical path
- Identify risks (complexity, external dependencies, knowledge concentration) with mitigations
- Sequence stories appropriately based on dependencies
- Generate a sprint plan summary with goal, capacity, committed stories, and risk register
How to install sprint-plan
npx skills add https://github.com/phuryn/pm-skills --skill sprint-planHow to use sprint-plan
- 1.Provide team roster with availability (PTO, meetings, on-call status)
- 2.Share historical velocity data from the last 3 sprints
- 3.Provide the prioritized backlog with story estimates and acceptance criteria
- 4.Share any previous sprint reports or capacity constraints
- 5.Review the generated sprint plan summary and adjust story selection or sequencing as needed
Use cases
- Preparing for a sprint planning meeting with capacity and story selection pre-work
- Balancing sprint scope when velocity is lower than backlog demand
- Identifying and mitigating risks before committing to stories
- Sequencing dependent stories to unblock parallel work
- Estimating realistic sprint capacity for a team with PTO or on-call rotations
- Scrum Masters
- Product Owners
- Engineering Managers
- Tech Leads
- Product Managers
sprint-plan FAQ
Flag the gap and work with the Product Owner to refine and estimate stories from the backlog. Consider pulling in tech debt or spike stories if available.
Map them explicitly, identify the owner, and flag them as risks. Sequence dependent stories after their blockers are complete, or negotiate with external teams for earlier delivery.
Reserve 15-20% of capacity for unexpected work, bugs, and tech debt. Adjust based on your team's historical context and known interruptions.
Write a single, clear sentence that describes what success looks like for the sprint—focus on value delivery, not task completion.
Flag it as a risk and consider breaking it down, adding a spike story for investigation, or deferring it to a future sprint.
Full instructions (SKILL.md)
Source of truth, from phuryn/pm-skills.
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
-
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
-
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
-
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
-
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
-
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] -
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
More from phuryn/pm-skills and the wider catalog.
sql-queries
Generate SQL queries from natural language across BigQuery, PostgreSQL, MySQL, and more.
stakeholder-map
Build a power/interest grid to map stakeholders and create targeted communication strategies.
startup-canvas
Generate a comprehensive Startup Canvas combining 9-section Product Strategy with Business Model for new products.
summarize-interview
Transform interview transcripts into structured summaries with JTBD, satisfaction signals, and action items.
summarize-meeting
Transform meeting transcripts into structured notes with decisions, action items, and clear ownership.
swot-analysis
Identify strengths, weaknesses, opportunities, and threats with strategic recommendations for competitive positioning.