sprint-planner

Plan Agile sprints with story estimation, capacity planning, and velocity tracking.

1|1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/yunseo-kim/agent-toolbox --skill sprint-planner-yunseo-kim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planner
Source: https://github.com/yunseo-kim/agent-toolbox/tree/main/catalog/skills/sprint-planner
Command: npx skills add https://github.com/yunseo-kim/agent-toolbox --skill sprint-planner-yunseo-kim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of Agile sprint planning, ensuring teams can effectively estimate stories, manage capacity, and set clear goals.

Core Features & Use Cases

  • Story Estimation: Utilizes a Modified Fibonacci sequence for story point estimation.
  • Capacity & Velocity Tracking: Calculates team capacity and tracks sprint velocity for predictable delivery.
  • Sprint Goal Setting: Facilitates the definition of clear, actionable sprint goals.
  • Use Case: A development team can use this skill to plan their next two-week sprint, estimating user stories, defining the sprint goal, and committing to a manageable backlog based on their historical velocity.

Quick Start

Use the sprint-planner skill to plan the next sprint with a team capacity of 20 points and a backlog of 5 user stories.

Frequently Asked Questions about sprint-planner

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

FAQPage Schema
How do I calculate team capacity for sprint planning based on available working days?

Sprint planning calculates team capacity by factoring in available working days and a focus factor. This determines the realistic workload a development team can commit to for a predictable delivery.

What is the Modified Fibonacci sequence used for in agile story point estimation?

The Modified Fibonacci sequence is used for agile story point estimation to size user stories. It provides a non-linear scale that helps scrum teams account for increasing uncertainty in larger backlog items.

How do I use historical velocity to prioritize a sprint backlog?

Historical velocity tracks completed story points to guide sprint backlog prioritization. By comparing past velocity against calculated team capacity, scrum masters can commit to a manageable workload.

Can I use this for defining sprint goals with a development team?

Yes, sprint planning facilitates defining clear and actionable sprint goals for a development team. This ensures the team aligns on objectives while estimating user stories and managing backlog prioritization.

What is the best way to estimate a two-week sprint with a specific point capacity?

To plan a two-week sprint, estimate user stories using Modified Fibonacci story points and compare the total against your team capacity. You commit to a backlog that aligns with the defined point capacity.

Does this sprint planning approach require a specific scrum framework to function?

No, it supports standard scrum practices but does not require a rigid framework. It focuses on core agile mechanics like story estimation, capacity calculation, and velocity tracking for sprint goal setting.