sprint-planner

Plan agile sprints by estimating stories and calculating capacity from historical velocity.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/rahulgupta2018/agent-skills --skill sprint-planner-rahulgupta2018
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planner
Source: https://github.com/rahulgupta2018/agent-skills/tree/main/skills/sprint-planner
Command: npx skills add https://github.com/rahulgupta2018/agent-skills --skill sprint-planner-rahulgupta2018

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the common issue of teams over-committing to work by providing a structured, velocity-based framework for sprint planning that accounts for capacity and focus factors.

Core Features & Use Cases

  • Velocity-Based Planning: Calculates realistic sprint commitments based on historical performance rather than optimistic capacity.
  • Definition of Done Enforcement: Standardizes the criteria for story completion to ensure quality and consistency.
  • Use Case: Use this during your bi-weekly iteration planning meeting to transform a raw backlog into a balanced, achievable sprint plan with clear goals and risk mitigation.

Quick Start

Activate the sprint-planner skill to generate a sprint plan for the upcoming iteration based on the current backlog and team velocity.

Frequently Asked Questions about sprint-planner

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

FAQPage Schema
How do I calculate sprint capacity using historical velocity in Scrum?

Sprint capacity is calculated by adjusting historical velocity with a focus factor to prevent over-commitment. This approach uses past performance data to generate realistic sprint commitments rather than relying on optimistic capacity estimates.

What is the best way to plan an agile sprint without over-committing the backlog?

The best way to avoid over-committing is velocity-based planning, which structures sprint commitments by estimating stories and calculating focus-factor-adjusted capacity to ensure the backlog is balanced and achievable.

How does relative point estimation work during backlog grooming?

Relative point estimation during backlog grooming assigns effort values to stories comparatively rather than by absolute hours. This standardizes the backlog items before they enter the sprint planning phase for capacity calculation.

Can I use focus factor adjustments for iteration planning in agile environments?

Yes, focus factor adjustments are applied during iteration planning to account for non-working time and risks. This modifies the raw historical velocity to calculate a realistic capacity for the upcoming sprint.

When do I need a Definition of Done for sprint planning?

A Definition of Done is needed during sprint planning to standardize the criteria for story completion. Enforcing it ensures quality and consistency across the sprint backlog before commitment.

Why does my sprint planning consistently fail to deliver the planned backlog stories?

Sprint planning often fails when teams commit to optimistic capacity rather than historical velocity. Applying focus-factor-adjusted capacity calculations and relative point estimation mitigates this risk and balances the sprint plan.