Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-develop/skills/sprint-planning

sprint-planning

Verified

Plan a sprint around a goal, real capacity, and named risks. Use when a team's sprints end with carryover, a pile of unrelated tickets, or a goal nobody can state.

FileKindSize
SKILL.mdskill md10.8 KB
examples/sample-industrial.mdmarkdown1.9 KB
examples/sample.mdmarkdown2.0 KB
template.mdmarkdown1.5 KB

template.md

View on GitHub
# Sprint Planning Template

The team sets capacity and estimates. Unsupplied figures stay `[NEEDS SOURCE]`.

---

## 1. Context
**Team:** · **Sprint length / dates:** · **Last sprint:** planned / completed / carried:
**Last three sprints' throughput:** [`NEEDS SOURCE` if unknown]

## 2. Sprint goal (one sentence, an outcome)
> [goal]
Specific? ☐ Valuable? ☐ Flexible (more than one way)? ☐

## 3. Capacity (set by the team)
| Person | Days in sprint | Leave / meetings / support | Focused days | Notes |
|---|---|---|---|---|
**Focus factor:** · **Team capacity:** · **Checked against recent throughput:** ☐
**Slack held (share, what it absorbs):**

## 4. Selected work
| Order | Item | Serves goal how | Ready? (understood, small, done defined) | Size (team's) | Stretch? |
|---|---|---|---|---|---|

Total vs capacity less slack:

## 5. Risks and dependencies
| Dependency / risk | Owner | Needed by | Fallback if it slips |
|---|---|---|---|
**Most likely to break the goal:**

## 6. Commitment
The team believes this plan: yes / no / with conditions: ____
**Review point:** [day five check]

---

## Quality checks
- [ ] Goal is specific, valuable, and flexible, written before the tickets
- [ ] Capacity is available focused hours, checked against recent throughput
- [ ] The team, not the PM, set the number
- [ ] Slack is held and its purpose named
- [ ] Every item serves the goal and is ready
- [ ] Every dependency has an owner, a date, and a fallback
- [ ] The team said aloud whether they believe it
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall