From product-management
Plans sprints by estimating capacity (PTO/meetings), prioritizing backlog, setting goals, identifying risks, and generating markdown plans. For kickoffs, sizing against availability, P0 decisions, carryover.
npx claudepluginhub anthropics/knowledge-work-plugins --plugin product-managementThis skill uses the workspace's default tool permissions.
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
Plans sprints in Scrum/agile projects: refines backlog items, defines sprint goal, calculates team capacity, selects items, decomposes into tasks, outputs SPRINT-PLAN.md. Use for new sprints or re-planning.
Plans sprints by estimating team capacity from velocity and availability, selecting stories from backlog, mapping dependencies, identifying risks, and defining sprint goals. Use for sprint planning, story selection, or capacity balancing.
Generates sprint plans with goals, prioritized backlogs, story point estimates, capacity breakdowns, agendas, and risks from user-provided backlog items.
Share bugs, ideas, or general feedback.
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.
/sprint-planning $ARGUMENTS
┌─────────────────────────────────────────────────────────────────┐
│ 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 │
└─────────────────────────────────────────────────────────────────┘
## 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 |