Sprint planning

Skill janellecipriano/pm-skills/skills/sprint-planning

Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.

Install

npx -y skills add janellecipriano/pm-skills --skill sprint-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Plan a sprint or iteration — sprint goal, available capacity, committed scope, and risks — from a backlog. Use when the user says "plan the sprint", "sprint planning", "what should we commit to this iteration", "groom the backlog into a sprint", or needs to turn priorities + capacity into a realistic commitment.

SKILL.md

1.9 KB, as published. Nobody here has run it

Sprint Planning

Turn a prioritized backlog and a known capacity into a realistic, goal-driven sprint commitment.

When to use

Planning the next sprint/iteration.
Sanity-checking whether a proposed commitment fits capacity.

Inputs to gather

Sprint length and start/end dates.
Team capacity: who's available, PTO/holidays, and any split focus. (See capacity-planning for deeper modeling.)
Candidate backlog items with priority and rough sizing (see estimation-sizing).
Carryover from the previous sprint.

Process

Define a single, crisp sprint goal — the outcome that makes this sprint a success. One sentence.
Compute available capacity (people × days − meetings/PTO − buffer). Reserve ~15–20% buffer for unknowns/support.
Pull items by priority that serve the goal until capacity is reached; stop there. Don't pad to 100%.
For each committed item, confirm it's ready (clear, sized, dependencies unblocked) — defer anything not ready.
Note risks/dependencies that could derail the sprint and who owns them.
State explicit stretch items separately from the commitment.

Output format

## Sprint {{n}} — {{dates}}
**Goal:** {{one sentence}}
**Capacity:** {{X person-days, after buffer}}

### Committed
| Item | Owner | Size | Notes |
| --- | --- | --- | --- |

### Stretch (only if commitment finishes early)
- {{item}}

### Risks / dependencies
- {{risk}} — owner {{name}}

Flag clearly if requested scope exceeds capacity, and recommend what to cut.