sprint-plan
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.
Security Assessment
About sprint-plan
Sprint Plan is a product-management skill that helps teams plan an agile sprint by estimating capacity, selecting and sequencing stories, mapping dependencies, and identifying risks. It addresses the common problem of over- or under-committing a sprint by grounding the plan in historical velocity and a realistic capacity buffer, and by surfacing dependencies and risks before work begins rather than mid-sprint.
The skill first reads any user-provided files such as backlogs, velocity data, team rosters, or previous sprint reports. It then follows a structured set of instructions: estimating team capacity from member availability (PTO, meetings, on-call) and average velocity over the last three sprints while reserving a 15-20% buffer for bugs and tech debt; reviewing and selecting stories from the prioritized backlog against a Definition of Ready and stopping when capacity is reached; mapping story and external-team dependencies to identify the critical path; identifying risks like high uncertainty, dependency slippage, and knowledge concentration along with mitigations; and producing a sprint-plan summary containing the sprint goal, duration, capacity, committed stories with points and owners, buffer, and a risks-with-mitigations list. It closes by defining a single-sentence sprint goal and saving the result as markdown.
It is aimed at product managers, scrum masters, product owners, and engineering leads preparing for sprint planning, estimating capacity, selecting stories, or balancing scope against velocity. It is a single-file SKILL.md that produces a planning document and includes a link to further reading on product owner versus product manager roles.
FAQ
What does the skill help me do during sprint planning?
It estimates team capacity, reviews and selects stories from the prioritized backlog, maps dependencies and the critical path, identifies risks with mitigations, and produces a sprint-plan summary with a clear sprint goal.
How does it estimate capacity?
It factors in team members and their availability such as PTO, meetings, and on-call, uses average velocity from the last three sprints, and reserves a 15-20% buffer for unexpected work, bugs, and tech debt.
Can it use my existing team data?
Yes. If you provide files like backlogs, velocity data, team rosters, or previous sprint reports, it reads them first and incorporates them into the plan.
What is the final output?
A markdown sprint-plan summary containing the sprint goal, duration, team capacity, committed stories with points and owners, remaining buffer, and a list of risks paired with mitigations.
Install sprint-plan
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
phuryn/pm-skills