skills.rest
tarunccet
tarunccetCOMMUNITY
Explore all skills by this author →
GitHub

sprint-plan

Estimate team capacity and sequence stories from backlog exports.

5|2|Updated Mar 27, 2026
Search Tags:#jira#velocity#dependency-mapping#sprint-planning#risk-identification#story-selection#capacity-estimation
One-click install
npx skills add https://github.com/tarunccet/pm-skills --skill sprint-plan-tarunccet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/tarunccet/pm-skills/tree/main/pm-execution/skills/sprint-plan
Command: npx skills add https://github.com/tarunccet/pm-skills --skill sprint-plan-tarunccet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines sprint planning by estimating team capacity, selecting and sequencing stories, and surfacing dependencies and risks so teams commit to a realistic, goal-oriented sprint.

Core Features & Use Cases

  • Capacity Estimation: Calculate available story points or ideal hours from team composition, availability, and historical velocity with a buffer for unplanned work.
  • Backlog Selection & Sequencing: Pull prioritized stories, verify Definition of Ready, stop at capacity, and sequence dependent work to reveal the critical path.
  • Risk Identification & Mitigation: Flag high-uncertainty stories, external dependencies, and single-point knowledge risks and propose mitigations.
  • Use Case: Convert a JIRA backlog export and team availability into a two-week sprint plan with a clear sprint goal, committed stories, owners, dependencies, and identified risks.

Quick Start

Create a two-week sprint plan from the attached backlog and team availability, estimating capacity, selecting committed stories, mapping dependencies, and listing risks with mitigations.

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 based on team capacity and backlog stories?▼

Sprint planning requires estimating team capacity from historical velocity and availability, then selecting and sequencing backlog stories until capacity is reached to produce a committed sprint scope and goal.

How do I calculate sprint capacity using historical velocity and team availability?▼

Sprint capacity is calculated by evaluating team composition and availability against historical velocity, then applying a buffer for unplanned work to determine the total available story points or ideal hours for the sprint.

How do I map dependencies and identify risks during sprint planning?▼

Dependency mapping sequences dependent work to reveal the critical path, while risk identification flags high-uncertainty stories, external dependencies, and single-point knowledge risks to propose actionable mitigations.

Can I use a Jira backlog export to create a two-week sprint plan?▼

Yes, you can apply sprint planning to short sprint cycles by using a Jira backlog export alongside team availability to generate a two-week sprint plan with committed stories, owners, and identified risks.

What do I need to create a committed sprint scope and goal?▼

You need a sprint backlog or story list and team composition with availability to calculate capacity, map dependencies, identify risk mitigations, and produce a committed sprint scope and goal.

Related Skills

Explore More Product & Management Skills→
phurynphuryn
25.0k

sprint-plan

Estimate team capacity, select backlog stories, map dependencies, and identify risks for sprint planning.

Community
Intermediate
skytiger6724skytiger6724
2

sprint-plan

Plan sprint capacity, story selection, dependencies, and risks for upcoming delivery windows.

Community
Intermediate
tygwantygwan
1

sprint

Control sprint lifecycles and track velocity and burndown metrics.

Community
Basic
sethdfordsethdford
2

Sprint Planning Assistant

Generate sprint plans and risk assessments from team capacity and velocity.

Community
Advanced