sprint-plan

Estimate team capacity, select stories, map dependencies, and identify risks for sprint planning.

Updated Mar 7, 2026

Search Tags:#agile #sprint planning #risk management #scrum #capacity planning #story selection

Ready to run

npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill sprint-plan-shalevamin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/shalevamin/The-_Ultimate_agents/tree/main/.claude/skills/sprint-plan
Command: npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill sprint-plan-shalevamin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of sprint planning by helping teams estimate capacity, select appropriate stories, and identify potential risks.

Core Features & Use Cases

Capacity Estimation: Calculates available story points or hours based on team size, availability, and historical velocity.
Story Selection: Guides the selection of stories from a prioritized backlog, ensuring they meet readiness criteria.
Dependency Mapping: Identifies and sequences stories with interdependencies and external dependencies.
Risk Identification: Flags potential risks such as high uncertainty, external blockers, or knowledge silos, and suggests mitigations.
Sprint Goal Definition: Helps articulate a clear, concise sprint goal.
Use Case: A Scrum Master can use this Skill at the start of a sprint planning meeting to facilitate a structured discussion and create a well-defined sprint backlog.

Quick Start

Use the sprint-plan skill to plan a sprint for the 'user-authentication' module.

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 and estimate team capacity for scrum?▼

Sprint planning calculates available story points by analyzing team size, member availability, and historical velocity to generate a structured sprint backlog and capacity summary.

What is the best way to map dependencies when selecting backlog stories for sprint planning?▼

Dependency mapping identifies and sequences stories with interdependencies and external blockers during sprint planning to ensure selected backlog stories meet readiness criteria.

How do I identify risks and blockers during agile sprint planning?▼

Risk identification flags potential sprint issues like high uncertainty, external blockers, and knowledge silos, providing actionable mitigations to secure the sprint goal.

Can I use this for capacity planning if my team has variable availability?▼

Yes, sprint planning accommodates variable availability by adjusting capacity calculations using team composition, individual availability, and historical velocity metrics.

What inputs do I need to generate a comprehensive sprint plan summary?▼

Generating a sprint plan summary requires team composition data, member availability, historical velocity metrics, and a prioritized agile backlog to drive story selection.

How do we define a clear sprint goal during sprint planning?▼

Defining a sprint goal is facilitated by aligning selected stories, mapped dependencies, and identified risks into a concise objective guiding the upcoming sprint execution.