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.
- Installs
- 2.7K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/phuryn/pm-skills --skill sprint-plan- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads sprint-plan automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
FAQ
What does the sprint-plan skill do?
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.
How do I install sprint-plan?
Run npx skills add https://github.com/phuryn/pm-skills --skill sprint-plan in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sprint-plan/ (personal) or .claude/skills/sprint-plan/ (project).
Which AI agents can use sprint-plan?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is sprint-plan safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains sprint-plan?
It is published by phuryn in phuryn/pm-skills. It has 2,741 recorded installs.
More from phuryn/pm-skills
create-prd
phuryn/pm-skills
Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
pre-mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
prioritization-frameworks
phuryn/pm-skills
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
outcome-roadmap
phuryn/pm-skills
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
strategy-red-team
phuryn/pm-skills
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
competitor-analysis
phuryn/pm-skills
Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.