sprint-plan
The sprint-plan skill guides teams through capacity estimation, story selection, dependency mapping, and risk identification to create a balanced sprint plan. Use it when preparing for sprint planning meetings, estimating how much work a team can realistically complete, selecting stories from a prioritized backlog, sequencing dependent work, or identifying potential blockers and risks that could impact sprint success.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/sprint-plan && cp -r /tmp/sprint-plan/pm-execution/skills/sprint-plan ~/.claude/skills/sprint-planSKILL.md
## 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)
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.