New to Claude Skills? Learn how to install them →

anthropics on GitHub

Sprint Planning

OfficialFree

Streamline your sprint planning process with structured guidance.

Get this skill

Free · Opens the source repo

What Sprint Planning does

The Sprint Planning skill provides a structured approach to planning sprints in agile development environments. It assists teams in defining sprint goals, estimating team capacity, and prioritizing backlog items effectively. By using this skill, teams can ensure that they have a clear understanding of their objectives and the resources available to achieve them. This clarity helps in managing expectations and improving overall team productivity.

When initiating a sprint, the skill prompts users to input key information such as team availability, sprint length, and prioritized backlog items. It also allows for consideration of any carryover tasks from previous sprints and identifies dependencies that may affect the current sprint. The output includes a comprehensive sprint plan document that outlines goals, capacity, backlog items, and risks, ensuring that all team members are aligned and aware of their responsibilities.

This skill is particularly beneficial for project managers, scrum masters, and team leads who are responsible for facilitating sprint planning sessions. It helps in creating a focused environment where teams can collaboratively decide what work to commit to, based on realistic capacity estimates. By incorporating this skill into their workflow, teams can enhance their sprint planning process, leading to more successful sprint outcomes and improved team morale.

When to use it

Use this skill when kicking off a new sprint or when needing to size a backlog against team availability, including considerations for PTO and meetings.

When not to use it

This skill may not be suitable for teams that do not follow agile methodologies or for those looking for a tool that integrates with specific project management software without manual input.

What you can build with it

Kicking Off a New Sprint

Use this skill to define clear goals and establish a plan for a new sprint, ensuring everyone is aligned.

Estimating Team Capacity

When preparing for a sprint, input team availability to accurately estimate how much work can be realistically completed.

Prioritizing Backlog Items

Utilize the skill to scope and prioritize backlog items based on urgency and team capacity, making sure critical tasks are addressed first.

How to install Sprint Planning

View source

1. Install with the skills CLI

npx skills add anthropics/knowledge-work-plugins/sprint-planning --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by anthropics

/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 $ARGUMENTS

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                        │
└─────────────────────────────────────────────────────────────────┘

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

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

Frequently asked questions about Sprint Planning

Similar skills