sprint-planning

Generate a Markdown sprint plan with committed and stretch stories and risks.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill sprint-planning-eric-pacheco95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/Eric-Pacheco95/claude-workbench/tree/main/.claude/skills/sprint-planning
Command: npx skills add https://github.com/Eric-Pacheco95/claude-workbench --skill sprint-planning-eric-pacheco95

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams plan sprints by applying team capacity and velocity to a refined backlog, resulting in a commit-ready sprint plan with committed and stretch stories, and explicit risks.

Core Features & Use Cases

  • Sprint Planning: Generate a sprint plan with committed and stretch stories based on team capacity and velocity.
  • Capacity Calculation: Calculate effective capacity considering historical data and team availability.
  • Committed Stories Selection: Prioritize and select committed stories based on priority and value.
  • Sprint Goal Identification: Establish a clear sprint goal that aligns with the team's objectives.
  • Risk Register: Identify and document risks associated with committed stories.
  • Plan Documentation: Generate a Markdown document outlining the sprint plan, including committed stories, stretch stories, and risks.

Quick Start

Use the /sprint-planning skill to create a sprint plan for "Sprint 24" with a velocity of 32 points and a team capacity of 45 days, using the refined backlog from 'history/lessons-learned/aml-review/refinement-prep-s24.md'.

Frequently Asked Questions about sprint-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a sprint plan from a refined backlog using team velocity and capacity?

Sprint planning requires a refined backlog, sprint name, project slug, velocity, and capacity as inputs. It then applies this data to produce a Markdown sprint plan document with committed stories, stretch stories, and a risk register.

What is the best way to calculate effective capacity for sprint planning?

Effective capacity for sprint planning is calculated by considering historical data and team availability. This ensures the sprint plan accurately reflects the team's actual capability for the upcoming sprint.

How does sprint planning handle risk assessment for committed stories?

Sprint planning handles risk assessment by identifying and documenting explicit risks associated with selected committed stories. These risks are compiled into a dedicated risk register within the final plan.

Can I prioritize committed stories based on value during sprint planning?

Yes, sprint planning prioritizes and selects committed stories based on priority and value. This ensures the most valuable items are included in the sprint plan according to your team's capacity.

What format is the final sprint plan and risk register output in?

The final sprint plan and risk register are output as a Markdown document. This document outlines committed stories, stretch stories, sprint goals, and explicit risks for the sprint.