/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.
Claude Code
$ npx -y skills add phuryn/pm-skills --skill sprint-plan --agent claude-code
Codex
$ npx skills add phuryn/pm-skills --skill sprint-plan -a codex -y
Cursor
$ npx skills add phuryn/pm-skills --skill sprint-plan -a cursor -y
Gemini CLI
$ npx skills add phuryn/pm-skills --skill sprint-plan -a gemini-cli -y
GitHub Copilot
$ npx skills add phuryn/pm-skills --skill sprint-plan -a github-copilot -y
OpenCode
$ npx skills add phuryn/pm-skills --skill sprint-plan -a opencode -y
Windsurf
$ npx skills add phuryn/pm-skills --skill sprint-plan -a windsurf -y
SKILL.md
sprint-plan.SKILL.mdname: 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)
Read more
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)
72 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Other skills on pm-skills.
More skills from other plugins.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
distilly
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…
openwork-connect
Search and use the skills, MCP connections, and connected services available through the user's OpenWork organization.
Questions about sprint-plan.
- Which coding agents can use sprint-plan?
- sprint-plan installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

