sprint-plan

Plan sprints with capacity estimation, story selection, dependency mapping, and risk identification.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill sprint-plan-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/moonzff/Codex_up/tree/main/skills/docs-meetings-writing/sprint-plan
Command: npx skills add https://github.com/moonzff/Codex_up --skill sprint-plan-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sprint planning often involves guesswork around team capacity, poorly sequenced stories, and overlooked risks, leading to overcommitment and missed sprint goals. This Skill structures the entire planning process so commitments are grounded in real velocity and availability data. ## Core Features & Use Cases - Capacity Estimation: Calculates available story points from team availability, historical velocity, and a 15-20% buffer for unexpected work. - Story Selection & Sequencing: Pulls prioritized backlog items, checks Definition of Ready, maps dependencies, and identifies the critical path. - Risk Identification: Flags high-uncertainty stories, external dependencies, and knowledge concentration with suggested mitigations. - Use Case: Before a two-week sprint, provide your backlog, last three sprints' velocity, and team PTO schedule to receive a committed story list, sprint goal, and risk register. ## Quick Start Ask the assistant to plan the next sprint using your backlog, team availability, and recent velocity data.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I estimate sprint capacity for my team?▼

Sprint capacity is estimated from team member availability (accounting for PTO, meetings, and on-call), average velocity from the last three sprints, and a 15-20% buffer for unexpected work. The result is expressed in story points or ideal hours.

How to select stories for a sprint from the backlog?▼

Pull stories from the prioritized backlog in priority order, verify each meets the Definition of Ready (clear acceptance criteria, estimated, no blockers), and stop adding stories once capacity is reached. Flag stories needing refinement before committing.

What inputs does sprint planning need to work well?▼

Sprint planning works best with a prioritized backlog, historical velocity data from recent sprints, and a team roster with availability details. Files like previous sprint reports or velocity spreadsheets can be provided as context.

How are sprint risks and dependencies identified?▼

Risks are identified by flagging stories with high uncertainty, external dependencies that could slip, and knowledge concentration where only one person can do the work. Each risk is paired with a suggested mitigation, and dependent stories are sequenced to reveal the critical path.

When should you not commit a story to a sprint?▼

Do not commit stories that lack clear acceptance criteria, are unestimated, have unresolved blockers, or exceed remaining team capacity. These should be flagged for refinement and deferred to a future sprint.