sprint-planning

Define sprint scope, estimate capacity, and output a markdown sprint plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product and engineering teams convert a prioritized backlog and team availability into a focused iteration plan by defining scope, estimating capacity, and setting measurable sprint goals to reduce overcommitment and unclear priorities.

Core Features & Use Cases

  • Define clear iteration goals and acceptance criteria so the team knows what success looks like.
  • Estimate team capacity taking into account vacations, meetings, and partial availability to produce realistic velocity and load calculations.
  • Prioritize backlog and allocate work into P0/P1/P2 categories, surface dependencies and risks, and produce a markdown-formatted sprint plan for kickoff and stakeholder sharing.
  • Use case: Run at sprint kickoff to produce a capacity table, a prioritized work breakdown, identified blockers, and a mitigation plan for a two-week engineering sprint.

Quick Start

Run /sprint-planning with the team roster, iteration length, availability notes, and a prioritized backlog to generate a complete sprint plan in markdown.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I create a sprint plan that accounts for team capacity and vacation?

Sprint planning converts your prioritized backlog and team availability into a structured iteration plan. It estimates capacity by factoring in vacations and meetings to produce realistic velocity calculations and a markdown sprint plan.

What is the best way to prioritize a backlog for an engineering sprint kickoff?

The best way to prioritize a backlog is allocating work into P0, P1, and P2 categories. This surfaces dependencies and risks while producing a markdown-formatted sprint plan for stakeholder sharing.

How do I estimate team velocity when members have partial availability?

To estimate team velocity with partial availability, calculate capacity by inputting team roster details and availability notes. The sprint plan adjusts velocity and load calculations based on actual working hours.

Can I handle leftover work from prior iterations during sprint planning?

Yes, sprint planning handles leftover work from prior iterations. It incorporates previous incomplete backlog items into the new iteration scope to ensure accurate capacity planning and risk mitigation.

How do I identify dependencies and blockers before a sprint starts?

To identify dependencies and blockers, input your backlog items and team roster into the sprint planning process. It surfaces these risks and generates a mitigation plan within the final markdown sprint document.