sprint-planning

Generates a structured sprint plan with capacity estimates, prioritized backlog, and risk tracking.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Nadav011/nadavai-claude --skill sprint-planning-nadav011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/Nadav011/nadavai-claude/tree/main/plugins/nadavai/skills/sprint-planning
Command: npx skills add https://github.com/Nadav011/nadavai-claude --skill sprint-planning-nadav011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sprint kickoffs often stall on scattered inputs: unclear team availability, unprioritized backlogs, and forgotten carryover. This Skill turns those raw inputs into a complete sprint plan document with goals, capacity math, and risk tracking. ## Core Features & Use Cases - Capacity Estimation: Calculates available team days and points while accounting for PTO, meetings, and on-call rotations. - Backlog Prioritization: Organizes work into P0 (must ship), P1 (should ship), and P2 (stretch) tiers with owners and dependencies. - Risk and Carryover Handling: Surfaces unfinished work from the previous sprint and documents risks with mitigations. - Use Case: A product manager kicking off a two-week sprint pastes the backlog and team availability, then receives a formatted sprint plan with a sprint goal, capacity table, key dates, and a definition of done checklist. ## Quick Start Ask the assistant to plan the next sprint by providing the sprint name or date range, team availability, and the prioritized backlog.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I plan a sprint with limited team capacity?

Provide each team member's available days accounting for PTO, meetings, and on-call duties. The Skill calculates total capacity in points and recommends planning to 70-80% of capacity to leave buffer for interrupts.

How to prioritize a sprint backlog into P0, P1, and P2?

Classify items as P0 (must ship), P1 (should ship), and P2 (stretch) with estimates, owners, and dependencies. Identifying stretch items upfront makes it clear what to cut if work takes longer than expected.

Can sprint planning integrate with Jira or other project trackers?

The Skill works standalone with pasted or described backlogs, and can optionally pull backlog items, create sprints, and assign work when a project tracker is connected. Calendar and chat integrations add PTO awareness and plan sharing.

How should carryover from the previous sprint be handled?

List unfinished items as carryover input and understand why they did not ship before re-committing them. The Skill includes carryover in the sprint backlog so it competes honestly for capacity against new work.

What makes a good sprint goal?

A good sprint goal states what success looks like in one clear sentence. If the goal cannot be expressed in a single sentence, the sprint is likely unfocused and the scope should be narrowed.