A structured approach to estimating capacity, selecting and sequencing stories, mapping dependencies, and identifying risks to create a cohesive sprint plan.

How is capacity calculated?

By counting team members and availability, using historical velocity from the last 3 sprints, and applying a 15-20% buffer for unknown work.

How are risks handled?

Identify high-uncertainty or dependency risks and document concrete mitigations for each, updating the plan accordingly.

sprint-plan

Scanned

npx machina-cli add skill phuryn/pm-skills/sprint-plan --openclaw

Files (1)

SKILL.md

2.3 KB

Sprint Planning

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

Context

You are helping plan a sprint for $ARGUMENTS.

If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.

Instructions

Estimate team capacity:
- Number of team members and their availability (PTO, meetings, on-call)
- Historical velocity (average story points per sprint from last 3 sprints)
- Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
- Calculate available capacity in story points or ideal hours
Review and select stories:
- Pull from the prioritized backlog (highest priority first)
- Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
- Flag stories that need refinement before committing
- Stop adding stories when capacity is reached
Map dependencies:
- Identify stories that depend on other stories or external teams
- Sequence dependent stories appropriately
- Flag external dependencies and owners
- Identify the critical path
Identify risks and mitigations:
- Stories with high uncertainty or complexity
- External dependencies that could slip
- Knowledge concentration (only one person can do it)
- Suggest mitigations for each risk

Create the sprint plan summary:

Sprint Goal: [One sentence describing what success looks like]
Duration: [2 weeks / 1 week / etc.]
Team Capacity: [X story points]
Committed Stories: [Y story points across Z stories]
Buffer: [remaining capacity]

Stories:
1. [Story title] — [points] — [owner] — [dependencies]
...

Risks:
- [Risk] → [Mitigation]

Define the sprint goal: A single, clear sentence that captures the sprint's primary value delivery.

Think step by step. Save as markdown.

Source

git clone https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/sprint-plan/SKILL.mdView on GitHub

Overview

Sprint-plan helps teams estimate capacity, select and sequence stories, map dependencies, and identify risks to balance sprint scope against velocity. It guides you from capacity estimation through a final plan and sprint goal. Practical, repeatable steps ensure readiness and alignment.

How This Skill Works

The skill starts by estimating capacity using team availability and last 3 sprints velocity, plus a 15-20% buffer. It then reviews the backlog, selecting stories that meet the Definition of Ready and stopping when capacity is reached. Next, it maps dependencies, flags external owners, and identifies risks with mitigations, finishing with a concise sprint plan summary and a clear sprint goal.

When to Use It

Before sprint planning to establish a data-driven capacity baseline
When prioritizing and selecting backlog items for the upcoming sprint
When identifying and sequencing dependent stories across teams
When balancing sprint scope against velocity to avoid overcommitment
When documenting the sprint goal, plan, and risk mitigations for stakeholders

Quick Start

Step 1: Gather backlog items, velocity data from last 3 sprints, and team availability
Step 2: Estimate capacity, review backlog, and select DoR-approved stories until capacity is reached
Step 3: Map dependencies, identify risks with mitigations, and publish the sprint plan and goal

Best Practices

Use historical velocity from the last 3 sprints to calibrate capacity
Apply a 15-20% capacity buffer for unexpected work and tech debt
Verify every selected story meets the Definition of Ready (AC, estimate, no blockers)
Stop adding stories once capacity is reached to avoid overcommitment
Identify risks and document mitigations for each risk (dependencies, knowledge concentration, etc.)

Example Use Cases

A team estimates capacity, selects 4 stories totaling 40 points, and sets a sprint goal with a 6-point buffer
Dependencies are identified with external teams and assigned owners before sprint start
The sprint plan summary includes Sprint Goal, Duration, Capacity, Committed Stories, and Risks
Two stories are refined mid-planning because they failed the Definition of Ready
Velocity from the last 3 sprints is used to set a realistic capacity and adjust backlog items

Frequently Asked Questions

Add this skill to your agents