sprint-plan

Generate a sprint plan with capacity estimation, story sequencing, and risk identification.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/martiraste-lgtm/claude-skills --skill sprint-plan-martiraste-lgtm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/martiraste-lgtm/claude-skills/tree/main/pm-execution-sprint-plan
Command: npx skills add https://github.com/martiraste-lgtm/claude-skills --skill sprint-plan-martiraste-lgtm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and optimize sprint planning by estimating capacity, selecting stories, mapping dependencies, and identifying risks to keep sprint scope aligned with velocity.

Core Features & Use Cases

  • Capacity estimation: compute available story points or hours based on team availability, PTO, meetings, and buffer.
  • Story selection & sequencing: pull from backlog by priority, ensure Definition of Ready, detect blockers, and stop when capacity is reached.
  • Dependency mapping & risk identification: identify inter-story and external dependencies, owners, and potential risks with mitigations.
  • Sprint plan summary: generate sprint goal, duration, committed stories, and risk mitigations.

Quick Start

Provide your backlog, velocity data, and team roster to generate a ready-to-execute sprint plan.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I plan a sprint using team velocity and backlog priority?

Sprint planning uses a deterministic workflow to estimate team capacity, sequence prioritized backlog stories, and generate a sprint plan summary with committed stories and risk mitigations.

How does sprint capacity calculation account for team availability and PTO?

Sprint capacity calculation computes available story points or hours by adjusting for team availability, PTO, meetings, and buffer, ensuring the committed backlog matches actual velocity.

What is the best way to map dependencies and identify risks during sprint planning?

Dependency mapping during sprint planning identifies inter-story and external dependencies with owners, flagging potential risks and generating mitigations to prevent sprint blockers.

How do I sequence backlog stories and check Definition of Ready before committing to a sprint?

Story selection pulls from the prioritized backlog, enforces Definition of Ready checks, detects blockers, and stops adding stories when the calculated team capacity is reached.

Can I generate a sprint plan summary with goals, occupancy, and risk mitigations?

Sprint plan generation outputs a coherent summary including the sprint goal, duration, committed stories, capacity occupancy, and risk mitigations based on the provided backlog and velocity data.