sprint-plan

Estimate team capacity and select prioritized backlog items for sprint planning.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Osirs/pm-skills-sc --skill sprint-plan-osirs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/Osirs/pm-skills-sc/tree/main/03-PM%E6%89%A7%E8%A1%8C%E7%AE%A1%E7%90%86/skills/sprint-plan
Command: npx skills add https://github.com/Osirs/pm-skills-sc --skill sprint-plan-osirs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps Product Managers and Scrum Masters plan sprints by estimating team capacity, selecting and prioritizing backlog items, mapping dependencies, and identifying potential risks.

Core Features & Use Cases

  • Capacity Estimation: Calculates available story points or ideal hours based on team size, availability, and historical velocity.
  • Story Selection: Selects prioritized backlog items that fit within the estimated capacity, ensuring they meet the Definition of Ready.
  • Dependency Mapping: Identifies and maps inter-story dependencies and external team dependencies.
  • Risk Identification: Flags potential risks and suggests mitigation strategies.
  • Sprint Goal Definition: Helps articulate a clear, single-sentence sprint goal.
  • Use Case: A Scrum team needs to plan their next two-week sprint. They provide their historical velocity, team member availability, and a prioritized backlog. The AI uses this Skill to propose a sprint backlog, identify potential blockers, and suggest a sprint goal.

Quick Start

Use the sprint-plan skill to plan a sprint for the attached backlog and team availability data.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I estimate team capacity for sprint planning using historical velocity?

Sprint planning estimates team capacity by calculating available story points or ideal hours based on team size, member availability, and historical velocity to determine how much work can be committed.

What is the best way to map story dependencies and identify risks in a sprint backlog?

Mapping story dependencies and identifying risks involves flagging inter-story dependencies, external team blockers, and suggesting mitigation strategies to ensure the prioritized backlog items can be completed.

How do I select prioritized backlog items that fit within estimated sprint capacity?

Selecting prioritized backlog items involves choosing stories that fit within the estimated team capacity while ensuring they meet the Definition of Ready before adding them to the sprint plan.

Can I use this sprint planning skill for a two-week Scrum sprint with varying team availability?

Yes, this skill handles sprint planning for Scrum teams by taking team member availability and historical velocity as input to generate a sprint plan summary tailored to iterative development cycles.

How do I define a clear sprint goal during backlog grooming and capacity planning?

Defining a sprint goal involves articulating a clear, single-sentence objective that aligns the selected backlog items and capacity planning with the overall sprint vision and priorities.

What inputs do I need to generate a sprint plan summary for an agile development team?

Generating a sprint plan summary requires inputs including team size, member availability, historical velocity, and a prioritized backlog to effectively estimate capacity and map dependencies.