sprint-planning

Calculate team capacity and identify risks for agile sprint planning.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/chavangorakh1999/sde-skills --skill sprint-planning-chavangorakh1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-execution/skills/sprint-planning
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill sprint-planning-chavangorakh1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams accurately plan their sprints by calculating real capacity, accounting for overhead, identifying risks, and ensuring a clear sprint goal, preventing overcommitment and scope creep.

Core Features & Use Cases

  • Capacity Calculation: Determines focused engineering hours available after accounting for meetings and interruptions.
  • Risk Management: Identifies and mitigates potential blockers and complexities in sprint tasks.
  • Commitment Guardrails: Provides heuristics for deciding which stories are safe to commit to.
  • Use Case: A development team can use this Skill to determine how many story points they can realistically commit to in a two-week sprint, considering team availability and known overhead.

Quick Start

Use the sprint-planning skill to plan a sprint for a team of 5 engineers over 10 days.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I calculate team capacity for sprint planning while accounting for meetings and PTO?

To calculate sprint capacity, subtract meeting hours, PTO, and overhead from total available hours to find focused engineering time. This prevents overcommitment by basing story point targets on actual availability.

What is the best way to identify dependencies and risks for agile user stories?

Identifying user story dependencies and risks involves assessing potential blockers and complexities within sprint tasks. This process provides heuristics for commitment decisions to ensure realistic sprint goals and mitigate scope creep.

How do I plan a two-week sprint for a team of 5 engineers?

Planning a two-week sprint for 5 engineers requires calculating capacity over 10 days, analyzing team availability, and evaluating story risks. This defines a clear sprint goal and identifies safe commitment guardrails.

Why does my scrum team consistently overcommit during sprint planning?

Scrum teams overcommit during sprint planning by ignoring overhead, meetings, and PTO when calculating capacity. Factoring in these interruptions and applying commitment heuristics prevents scope creep and ensures realistic story commitments.

Can I use agile capacity planning for risk management and defining sprint goals?

Agile capacity planning supports risk management by identifying dependencies and blockers, which directly informs sprint goal definition. This approach ensures commitments are guarded by heuristics based on available focused engineering hours.