iteration-planner

Plan sprint scope and task allocation from capacity and historical velocity.

12|2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/haomingz/kimi-skills --skill iteration-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iteration-planner
Source: https://github.com/haomingz/kimi-skills/tree/main/skills/iteration-planner
Command: npx skills add https://github.com/haomingz/kimi-skills --skill iteration-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning requires coordinating capacity, velocity, and backlog to produce an actionable plan. This skill guides teams to compute capacity, set sprint scope, break down stories, analyze dependencies, and balance workload to generate an executable sprint plan. It helps Scrum Masters and Product Teams align on goals across a sprint and avoid overcommitment or bottlenecks.

Core Features & Use Cases

  • Capacity-driven sprint scoping based on team velocity and available days.
  • Story splitting, estimation, and dependency analysis to unlock feasible sprint commitments.
  • Output of an executable sprint plan with assignment and risk checks.

Quick Start

Provide team capacity, velocity history, and backlog, then generate a ready-to-execute sprint plan.

Frequently Asked Questions about iteration-planner

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

FAQPage Schema
How do I calculate sprint capacity using team velocity?

Sprint planning uses historical velocity and available team capacity to determine sprint scope. It maps backlog prioritization, splits stories, and analyzes dependencies to generate an executable plan with balanced workload assignments.

How do I map dependencies when planning a sprint?

Dependency mapping during sprint planning involves analyzing backlog stories to identify bottlenecks and cross-task dependencies. This assessment allows teams to sequence work effectively and mitigate risks before finalizing sprint commitments.

Can I split user stories for sprint planning based on capacity?

Yes, story splitting is applied during sprint scoping to break down backlog items into feasible commitments. This ensures tasks fit within the calculated team capacity and align with historical velocity constraints.

What is the best way to avoid overcommitment in sprint planning?

To avoid overcommitment, sprint planning must be driven by calculated team capacity and historical velocity. Assessing dependencies and balancing workload across the team ensures the final sprint scope remains executable and risk-aware.

Do I need a prioritized backlog to start sprint planning?

Yes, a prioritized backlog is required alongside team capacity and velocity history. These inputs allow the planning process to sequence stories, map dependencies, and generate a ready-to-execute sprint plan with accurate risk checks.