Sprint Planning
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The sprint-planning skill provides a structured framework for teams to organize their upcoming work cycles. It helps teams account for individual availability, including PTO and meetings, to determine realistic capacity. By facilitating the prioritization of backlog items into P0, P1, and stretch goals, the skill ensures teams remain focused on high-impact objectives while managing dependencies and risks. The output is a comprehensive sprint plan document that includes capacity tables, backlog assignments, risk assessments, and a definition of done.
What it does
- Calculates team capacity based on individual availability and time constraints.
- Prioritizes backlog items into distinct tiers of importance.
- Identifies potential project risks and mitigation strategies.
- Generates a standardized sprint plan document with key dates and goals.
- Integrates with project trackers and calendars to automate data gathering.
- Defines clear success criteria and a definition of done for the sprint.
When to use it
- At the start of a new sprint cycle to establish team focus.
- When sizing a backlog against current team availability.
- When managing carryover tasks from a previous sprint.
- When determining which tasks are essential versus stretch goals.
Advantages
- Promotes realistic planning by accounting for non-coding time like meetings and PTO.
- Ensures sprint focus through the creation of a single, clear sprint goal.
- Provides a consistent format for sprint documentation across the team.
- Helps identify and mitigate risks before the sprint begins.
Usage examples
- “Plan the next two-week sprint for our team of 5 engineers.”
- The agent generates a structured sprint plan template, prompting for team availability, backlog items, and any carryover tasks to populate the capacity and backlog tables.
- “Help me prioritize our backlog for the upcoming sprint.”
- The agent assists in categorizing items into P0, P1, and stretch goals based on the team's estimated capacity and project dependencies.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/sprint-planning/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip sprint-planning.zip -d .agents/skills
Documentation by Anthropic
/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.
Usage
/sprint-planning $ARGUMENTSHow 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 │
└─────────────────────────────────────────────────────────────────┘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?
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 |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.
Files
- ATTRIBUTION.mdAdded by AutoGineer966 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md4.0 KiB
SKILL.md
/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.
Usage
/sprint-planning $ARGUMENTSHow 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 │
└─────────────────────────────────────────────────────────────────┘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?
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 |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.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · product-management/skills/sprint-planning · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from product-management/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.
Related skills
To Tickets
Matt Pocock· Community
Break complex plans into actionable, dependency-aware tracer-bullet tickets for your issue tracker.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
To Questionnaire
Matt Pocock· Community
Generate structured discovery questionnaires to extract missing information from stakeholders.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Internal Comms
AnthropicOfficial
A structured framework for drafting professional internal communications across various organizational formats.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0GitHub stars of the source repository188.6k
Events
Corey Haines· Community
A comprehensive framework for planning, executing, and measuring event-driven marketing to drive measurable business pipeline.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository59k
Office Hours
AnthropicOfficial
Facilitate team support by setting up and managing recurring office hours for collaborative problem-solving.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0GitHub stars of the source repository46.3k
Hackathon
AnthropicOfficial
Plan and organize a team hackathon, either by sourcing projects from your existing backlog or through open-ended creative experimentation.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0GitHub stars of the source repository46.3k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download sprint-planning.zip