Skills › Knowledge Work Plugins › sprint-planning

sprint-planning

skill · 94 lines · Apache-2.0 · product-management/skills/sprint-planning/SKILL.md

The facts

Its description

Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent picks this skill when someone is starting or preparing a sprint and wants help scoping the work, sizing it against the team's real availability, and writing up a plan. It also fits questions about what is P0 versus stretch, or what to do with items that did not finish last sprint.

Things a person might say (the model's guesses)

“Help me plan the next two-week sprint for my team”
“We're kicking off sprint 14 on Monday — can you draft the plan?”
“I need to figure out what we can actually fit this sprint given two people are on PTO”

A model's summary of when it is used.

A model's reading

What it takes when started

[sprint name or date range]

What to type after its name when you start it.

From its settingsline 4

Licence

Apache-2.0, from product-management/LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub

1---

2name: sprint-planning

3description: Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.

4argument-hint: "[sprint name or date range]"

5---

7# /sprint-planning

9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).

11Plan a sprint by scoping work, estimating capacity, and setting clear goals.

/sprint-planning

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Plan a sprint by scoping work, estimating capacity, and setting clear goals.

Raw lines 1 to 12

Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close

13## Usage

15```

16/sprint-planning $ARGUMENTS

17```

19## How It Works

21```

22┌─────────────────────────────────────────────────────────────────┐

23│ SPRINT PLANNING │

24├─────────────────────────────────────────────────────────────────┤

25│ STANDALONE (always works) │

26│ ✓ Define sprint goals and success criteria │

27│ ✓ Estimate team capacity (accounting for PTO, meetings) │

28│ ✓ Scope and prioritize backlog items │

29│ ✓ Identify dependencies and risks │

30│ ✓ Generate sprint plan document │

31├─────────────────────────────────────────────────────────────────┤

32│ SUPERCHARGED (when you connect your tools) │

33│ + Project tracker: Pull backlog, create sprint, assign items │

34│ + Calendar: Account for PTO and meetings in capacity │

35│ + Chat: Share sprint plan with the team │

36└─────────────────────────────────────────────────────────────────┘

37```

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                    SPRINT PLANNING                                 │
├─────────────────────────────────────────────────────────────────┤
│  STANDALONE (always works)                                       │
│  ✓ Define sprint goals and success criteria                     │
│  ✓ Estimate team capacity (accounting for PTO, meetings)        │
│  ✓ Scope and prioritize backlog items                           │
│  ✓ Identify dependencies and risks                              │
│  ✓ Generate sprint plan document                                │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + Project tracker: Pull backlog, create sprint, assign items   │
│  + Calendar: Account for PTO and meetings in capacity           │
│  + Chat: Share sprint plan with the team                        │
└─────────────────────────────────────────────────────────────────┘

Raw lines 19 to 38

39## What I Need From You

41- **Team**: Who's on the team and their availability this sprint?

42- **Sprint length**: How many days/weeks?

43- **Backlog**: What's prioritized? (Pull from tracker, paste, or describe)

44- **Carryover**: Anything unfinished from last sprint?

45- **Dependencies**: Anything blocked on other teams?

What I Need From You

Team: Who's on the team and their availability this sprint?
Sprint length: How many days/weeks?
Backlog: What's prioritized? (Pull from tracker, paste, or describe)
Carryover: Anything unfinished from last sprint?
Dependencies: Anything blocked on other teams?

Raw lines 39 to 46

47## Output

49```markdown

50## Sprint Plan: [Sprint Name]

51**Dates:** [Start] — [End] | **Team:** [X] engineers

52**Sprint Goal:** [One clear sentence about what success looks like]

54### Capacity

56|--------|---------------|------------|-------|

58| **Total** | **[X]** | **[X] points** | |

60### Sprint Backlog

62|----------|------|----------|-------|--------------|

67### Planned Capacity: [X] points | Sprint Load: [X] points ([X]% of capacity)

69### Risks

70| Risk | Impact | Mitigation |

71|------|--------|------------|

72| [Risk] | [What happens] | [What to do] |

74### Definition of Done

75- [ ] Code reviewed and merged

76- [ ] Tests passing

77- [ ] Documentation updated (if applicable)

78- [ ] Product sign-off

80### Key Dates

81| Date | Event |

82|------|-------|

83| [Date] | Sprint start |

84| [Date] | Mid-sprint check-in |

85| [Date] | Sprint end / Demo |

86| [Date] | Retro |

87```

Output

## Sprint Plan: [Sprint Name]
**Dates:** [Start] — [End] | **Team:** [X] engineers
**Sprint Goal:** [One clear sentence about what success looks like]

### Capacity
| Person | Available Days | Allocation | Notes |
|--------|---------------|------------|-------|
| [Name] | [X] of [Y] | [X] points/hours | [PTO, on-call, etc.] |
| **Total** | **[X]** | **[X] points** | |

### Sprint Backlog
| Priority | Item | Estimate | Owner | Dependencies |
|----------|------|----------|-------|--------------|
| P0 | [Must ship] | [X] pts | [Person] | [None / Blocked by X] |
| P1 | [Should ship] | [X] pts | [Person] | [None] |
| P2 | [Stretch] | [X] pts | [Person] | [None] |

### Planned Capacity: [X] points | Sprint Load: [X] points ([X]% of capacity)

### Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | [What happens] | [What to do] |

### Definition of Done
- [ ] Code reviewed and merged
- [ ] Tests passing
- [ ] Documentation updated (if applicable)
- [ ] Product sign-off

### Key Dates
| Date | Event |
|------|-------|
| [Date] | Sprint start |
| [Date] | Mid-sprint check-in |
| [Date] | Sprint end / Demo |
| [Date] | Retro |

Raw lines 47 to 88

89## Tips

911. **Leave buffer** — Plan to 70-80% capacity. You will get interrupts.

922. **One clear sprint goal** — If you can't state it in one sentence, the sprint is unfocused.

933. **Identify stretch items** — Know what to cut if things take longer than expected.

944. **Carry over honestly** — If something didn't ship, understand why before re-committing.

Tips

Leave buffer — Plan to 70-80% capacity. You will get interrupts.
One clear sprint goal — If you can't state it in one sentence, the sprint is unfocused.
Identify stretch items — Know what to cut if things take longer than expected.
Carry over honestly — If something didn't ship, understand why before re-committing.

Raw lines 89 to 94

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.