sprint-plan

Plans a sprint by estimating team capacity, selecting stories, and identifying risks.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill sprint-plan-choi-keith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/Choi-Keith/skill-arsenal-ultra/tree/main/plugins/pm-skills/pm-execution/skills/sprint-plan
Command: npx skills add https://github.com/Choi-Keith/skill-arsenal-ultra --skill sprint-plan-choi-keith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sprint planning meetings often suffer from overcommitment, unclear dependencies, and unaddressed risks. This Skill structures the entire sprint planning process so teams commit to a realistic scope based on actual capacity rather than guesswork. ## Core Features & Use Cases - Capacity Estimation: Calculates available story points from team availability, historical velocity, and a 15-20% buffer for unplanned work. - Story Selection & Dependency Mapping: Pulls prioritized backlog items, verifies Definition of Ready, sequences dependent stories, and flags external blockers. - Risk Identification: Surfaces high-uncertainty stories, knowledge silos, and at-risk external dependencies with mitigation suggestions. - Use Case: Before a sprint planning meeting, provide your backlog, recent velocity data, and team roster to receive a complete sprint plan summary with a sprint goal, committed stories, and risk register. ## Quick Start Ask the AI to plan the next two-week sprint using your prioritized backlog, the team's average velocity from the last three sprints, and current team availability.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I plan a sprint with story points?

Estimate team capacity from member availability and average velocity over the last three sprints, then pull prioritized backlog stories until reaching that capacity. Reserve 15-20% buffer for bugs and unplanned work before committing.

How to estimate sprint capacity for a team?

Calculate capacity by counting team members, subtracting PTO and meeting time, and multiplying by historical velocity per person. Express the result in story points or ideal hours, keeping a buffer for technical debt and interruptions.

What is Definition of Ready in sprint planning?

Definition of Ready means a story has clear acceptance criteria, has been estimated, and has no unresolved blockers before entering a sprint. Stories failing these checks should be flagged for further refinement rather than committed.

Can this handle dependencies between sprint stories?

Yes, the planning process identifies stories depending on other stories or external teams, sequences them appropriately, and flags external dependencies with owners. It also highlights the critical path across committed work.

What are limitations of velocity-based sprint planning?

Velocity-based planning assumes stable team composition and consistent estimation practices, so it degrades with new teams or changing scope. It also cannot account for unknown external delays, which is why explicit risk identification and buffers are included.