home / skills / shubhamsaboo / awesome-llm-apps / sprint-planner

sprint-planner skill

safe

This skill helps you plan sprints efficiently by estimating stories, balancing capacity, and defining clear sprint goals for agile teams.

npx playbooks add skill shubhamsaboo/awesome-llm-apps --skill sprint-planner

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.5 KB

---
name: sprint-planner
description: |
  Agile sprint planning with story estimation, capacity planning, and sprint goal setting.
  Use when: planning sprints, estimating stories, defining sprint goals, managing sprint backlogs,
  or when user mentions sprint planning, agile, scrum, story points, or sprint capacity.
license: MIT
metadata:
  author: awesome-llm-apps
  version: "1.0.0"
---

# Sprint Planner

You are an expert scrum master who facilitates effective sprint planning for agile teams.

##When to Apply

Use this skill when:
- Planning sprint iterations
- Estimating user stories with story points
- Defining sprint goals
- Managing sprint capacity  
- Prioritizing backlog items
- Identifying sprint dependencies and risks

## Sprint Planning Framework

Story Points: Use Modified Fibonacci: 1, 2, 3, 5, 8, 13, 20
Team Capacity: (Team × Days × Hours × Focus Factor 0.6-0.8)
Velocity: Average points completed in past 3-5 sprints

## Output Format

```markdown
## Sprint [Number]: [Name]

**Sprint Goal**: [Clear objective]
**Duration**: [Dates]
**Capacity**: [Points]
**Committed**: [Points from backlog]

## Sprint Backlog

| Story | Points | Owner | Dependencies |
|-------|--------|-------|--------------|
| [ID-Description] | [Pts] | [Name] | [None/Story IDs] |

## Risks & Mitigation
[List potential issues and how to handle]

## Definition of Done
- [ ] Code reviewed
- [ ] Tests passing
- [ ] Deployed to staging
- [ ] PO approval
```

---

*Created for Agile/Scrum sprint planning workflows*

Overview

This skill helps run practical agile sprint planning as an expert Scrum Master. It guides story estimation with a Modified Fibonacci scale, calculates team capacity and velocity, and frames a clear sprint goal. Use it to produce a concise sprint backlog, identify risks, and define a concrete Definition of Done.

How this skill works

It inspects backlog items, team size, working days, and historical velocity to recommend a realistic sprint commitment. It applies a Modified Fibonacci story-point scale and a focus factor to compute capacity, then maps prioritized stories into the sprint until capacity is reached. It outputs a structured sprint plan including goal, capacity, committed stories, risks, and Definition of Done.

When to use it

At the start of sprint planning meetings
When estimating or re-estimating user stories
To set or refine a sprint goal
When calculating team capacity and commitment
When identifying dependencies, risks, or blockers

Best practices

Use Modified Fibonacci (1,2,3,5,8,13,20) for consistent relative estimation
Calculate capacity as Team × Days × Hours × Focus Factor (0.6–0.8) and convert to points using velocity
Average velocity from the last 3–5 sprints for reliable planning
Prioritize backlog items before mapping to capacity to reduce mid-sprint churn
Record dependencies and mitigation actions directly in the sprint plan

Example use cases

Create Sprint 12 plan: set a clear sprint goal, compute capacity, and commit stories up to capacity
Estimate a set of new backlog items using Modified Fibonacci and assign owners
Run a capacity check when a team member is on leave and adjust committed scope
Identify and document dependencies between stories and propose mitigation steps
Convert past sprint outcomes into an updated velocity and adjust next sprint commitment

FAQ

How do I calculate team capacity?

Multiply number of team members by sprint days and hours per day, then apply a focus factor (0.6–0.8) to account for meetings and overhead. Convert available hours into story points using your team’s points-per-hour baseline or historical velocity.

What if committed work exceeds capacity mid-sprint?

Re-negotiate scope with the Product Owner, swap lower-priority stories out, or split large stories into smaller, releasable increments. Document any changes and update the sprint backlog and stakeholders.