agentleFS
nisarthnisarth/claude-skills-store/skills/product-management/sprint-planning/SKILL.md

sprint-planning

Skill1 starsChanged 7 months agoMITView on GitHub

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 is P0 vs. stretch, or handling carryover from the previous sprint. Trigger phrases: "sprint planning", "plan the sprint", "what should we take on", "scope the sprint", "sprint capacity", "carryover items", "sprint goals", "estimate capacity", "sprint backlog", "next sprint"

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sprint-review and retrospective.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nobufumi-tegoSkill

    sprint-review

    スプリント終了時に実行。DoD確認・デプロイ・CLAUDE.md更新・レトロ記録を行う。

    Also in 4 projects that use this

  • MicrosoftSkill

    retrospective

    Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before planning forward, close the loop:

    line 18
  2. Distinctive:

    Write 1-3 sprint goals that describe outcomes, not tasks:

    line 61
  3. Distinctive:

    Verify: P0 items should consume no more than 60% of capacity.

    line 98
  4. Distinctive:

    Protect focus time: If engineers have fewer than 4 uninterrupted hours per day, velocity will suffer regardless of capacity calculations.

    line 168
  5. Distinctive:

    Sprint goals drive prioritization: If an item does not contribute to a sprint goal, question whether it belongs in this sprint.

    line 169
  6. Distinctive:

    Review mid-sprint: Check progress at the halfway point.

    line 170

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sprint Planning

Plan sprints with realistic capacity estimation, clear goals, balanced scope, and structured commitment. Handle carryover, PTO, and team dynamics.

Workflow

Step 1: Review Previous Sprint

Before planning forward, close the loop:

  1. What shipped? List completed items and their outcomes.
  2. What carried over? Items that were committed but not finished. Why?
  3. What was unplanned? Work that entered the sprint after planning. How much capacity did it consume?
  4. Velocity: Actual points/items completed vs. planned.
  5. Patterns: Is carryover increasing? Is unplanned work growing? Are estimates consistently off?
### Sprint [N-1] Retrospective Summary
- Committed: [X] points/items
- Completed: [Y] points/items
- Carryover: [Z] points/items
- Unplanned: [W] points/items
- Velocity: [Y/X]%

Step 2: Calculate Capacity

Per-person capacity (for a 2-week sprint):

FactorDays
Total working days10
Minus PTO/holidays-[X]
Minus meetings/ceremonies-1.5
Minus on-call/support rotation-[X]
Minus overhead (code review, etc.)-1
Available days[Result]

Team capacity:

| Team Member | Role | Available Days | Notes |
|-------------|------|---------------|-------|
| [Name] | [Role] | [Days] | [PTO, half-sprint, etc.] |
| [Name] | [Role] | [Days] | |
| **Total** | | **[Sum]** | |

Apply a buffer: plan to 80% of calculated capacity. The remaining 20% absorbs unplanned work, estimation errors, and context switching.

Step 3: Define Sprint Goals

Write 1-3 sprint goals that describe outcomes, not tasks:

### Sprint [N] Goals

1. **[Goal]**: [What success looks like and why it matters]
2. **[Goal]**: [What success looks like and why it matters]
3. **[Goal]**: [What success looks like and why it matters (stretch)]

Good sprint goals:

  • "Users can complete checkout without errors on mobile" (outcome)
  • "Ship the billing page redesign to 100% of users" (deliverable with clear scope)

Bad sprint goals:

  • "Work on billing" (vague)
  • "Complete 8 tickets" (activity, not outcome)

Step 4: Scope the Backlog

Organize work into tiers:

P0 - Must complete (core sprint commitment):

ItemSizeOwnerDependencyGoal
[Item][S/M/L or points][Name][None/Item]Goal 1

P1 - Should complete (high-value, commit if capacity allows):

ItemSizeOwnerDependencyGoal
[Item][S/M/L or points][Name][None/Item]Goal 2

Stretch - Could complete (pulled in only if P0 and P1 are done):

ItemSizeOwner
[Item][S/M/L or points][Name]

Verify: P0 items should consume no more than 60% of capacity. P0 + P1 should not exceed 80%.

Step 5: Validate and Finalize

Checklist before committing:

  • P0 scope fits within 60% of team capacity
  • Each item has a clear owner
  • Dependencies are identified and sequenced
  • Carryover items are re-estimated (not assumed to be "almost done")
  • No single person is overloaded relative to others
  • Sprint goals are achievable with P0 items alone
  • QA and review time is accounted for
  • On-call rotation is factored in

Step 6: Draft the Sprint Plan

## Sprint [N] Plan
[Start Date] - [End Date]

### Goals
1. [Goal 1]
2. [Goal 2]
3. [Goal 3 - stretch]

### Team Capacity
[Capacity table]
Total available: [X] person-days | Planning to: [0.8X] person-days

### Committed Work (P0)
[Item table with sizes and owners]
Subtotal: [X] points/days

### Planned Work (P1)
[Item table]
Subtotal: [X] points/days

### Stretch
[Item list]

### Risks and Dependencies
- [Risk 1]: [Mitigation]
- [Dependency 1]: [Status]

### Carryover from Sprint [N-1]
- [Item]: [Reason for carryover] | Re-estimated: [Size]

Examples

Example 1: Standard Sprint

User: "Help me plan next sprint for a team of 5." Response: Calculate capacity (50 person-days minus PTO, meetings, overhead). Propose 2 sprint goals. Help prioritize backlog items into P0/P1/Stretch tiers. Validate that P0 fits within 60% of capacity.

Example 2: Heavy Carryover

User: "We have 6 items carrying over from last sprint." Response: First, diagnose why. Over-commitment, scope creep, or blockers? Re-estimate each carryover item (do not assume original estimate). Prioritize: some may no longer be P0. Reduce new commitments to accommodate carryover.

Example 3: Reduced Capacity

User: "Two engineers are on PTO next sprint." Response: Recalculate capacity. Identify which planned items depend on the absent engineers. Propose a reduced scope with fewer sprint goals. Flag any commitments at risk.

Best Practices

  1. Yesterday's weather. The best predictor of next sprint's velocity is last sprint's velocity. Do not plan for ideal conditions.
  2. Re-estimate carryover. "Almost done" is the most dangerous estimate. Carryover items frequently take longer than the remaining estimate suggests.
  3. Leave room for the unexpected. Teams that plan to 100% capacity always miss. Plan to 80% and deliver 100% of commitments instead.
  4. One owner per item. Shared ownership means no ownership. One person is responsible for each ticket, even if multiple people contribute.
  5. Size uncertainty, not just effort. An item that "should be small but might be large" is a Large, not a Small with a risk note.
  6. Protect focus time. If engineers have fewer than 4 uninterrupted hours per day, velocity will suffer regardless of capacity calculations.
  7. Sprint goals drive prioritization. If an item does not contribute to a sprint goal, question whether it belongs in this sprint.
  8. Review mid-sprint. Check progress at the halfway point. If P0 items are at risk, cut P1 and Stretch early rather than crunching at the end.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.