sprint-planning

Generates a sprint plan document from team capacity, backlog items, and dependencies.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill sprint-planning-ngochuy13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/sprint-planning
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill sprint-planning-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning helps teams turn a backlog into a realistic, goal-driven plan that fits actual capacity while accounting for PTO, meetings, carryover work, and dependencies.

Core Features & Use Cases

  • Capacity-aware scoping: Estimates how much work can fit in the sprint while accounting for time off and recurring commitments.
  • Clear goals and prioritization: Translates backlog items into P0/P1/P2 groupings aligned to sprint success criteria.
  • Risk and dependency planning: Surfaces blocked work, external dependencies, and mitigation plans so the team can execute with less churn.
  • Carryover handling: Reassesses unfinished items from the previous sprint and re-commits (or re-scope) them with context.

Quick Start

Use the sprint-planning skill to generate a complete sprint plan for your next sprint by providing your team, sprint length, prioritized backlog, and any carryover or dependencies.

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 accurate team capacity for PTO and meetings?

Sprint planning calculates actual team capacity by capturing availability inputs, estimating workload allocation, and accounting for PTO and recurring meetings to scope achievable sprint goals.

What is the best way to prioritize a backlog into P0, P1, and P2 categories?

Backlog prioritization groups items into P0, P1, and P2 categories aligned to sprint success criteria, distinguishing core commitments from stretch goals for realistic execution.

How do I handle carryover work from a previous sprint cycle?

Sprint planning reassesses unfinished carryover items from the previous cycle, allowing you to re-commit or re-scope them with context before finalizing the upcoming sprint plan.

Can I identify external dependencies and risks during sprint kickoff?

Yes, sprint planning surfaces blocked work and external dependencies during kickoff, generating mitigation plans so the team can execute with less churn and unexpected delays.

What information do I need to generate a structured sprint plan document?

You need to provide your team details, sprint length, prioritized backlog, and any carryover or dependencies to produce a structured sprint plan document with achievable goals.