sprint-plan

Plans agile sprints with capacity estimation, story selection, dependency mapping, and risk identification.

Updated Apr 8, 2026

Search Tags:#agile #sprint planning #backlog #story points #scrum #velocity #capacity estimation

One-click install

npx skills add https://github.com/stefanomartiradonna/claude-skills --skill sprint-plan-stefanomartiradonna

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/stefanomartiradonna/claude-skills/tree/main/pm-execution-sprint-plan
Command: npx skills add https://github.com/stefanomartiradonna/claude-skills --skill sprint-plan-stefanomartiradonna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sprint planning often fails because teams overcommit, ignore dependencies, or skip risk analysis, leading to missed sprint goals. This Skill structures the entire planning session so capacity, story selection, and risks are all addressed systematically. ## Core Features & Use Cases - Capacity Estimation: Calculates available story points from team availability, historical velocity over the last 3 sprints, and a 15-20% buffer for unexpected work. - Story Selection & Sequencing: Pulls stories from the prioritized backlog, checks Definition of Ready, maps dependencies, and identifies the critical path. - Risk Identification: Flags high-uncertainty stories, external dependencies, and knowledge concentration, with a mitigation for each risk. - Use Case: A product manager preparing for sprint planning provides the backlog, velocity data, and team roster, and receives a complete sprint plan summary with goal, committed stories, owners, and risk mitigations. ## Quick Start Plan a two-week sprint for my team of five using the attached backlog and velocity data from our last three sprints.

Frequently Asked Questions about sprint-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are the limitations of velocity-based sprint planning?▼

Velocity-based planning assumes stable team composition and consistent estimation, so it degrades with new teams, changing scope, or inconsistent story sizing. The 15-20% buffer mitigates this partially, but high-uncertainty stories still require explicit risk identification.