Create comprehensive sprint plans by intelligently grouping estimated user stories based on velocity, dependencies, priorities, and risk. This skill should be used during sprint planning ceremonies to transform backlog into actionable sprint commitments.
Instrucciones de origen · Vista previa de solo lectura
name
sprint-plan
description
Create comprehensive sprint plans by intelligently grouping estimated user stories based on velocity, dependencies, priorities, and risk. This skill should be used during sprint planning ceremonies to transform backlog into actionable sprint commitments.
acceptance
[{"velocity_respected":"Total story points ≤ team velocity with 15% buffer"},{"dependencies_satisfied":"All story dependencies respected in sprint ordering"},{"priorities_honored":"P0 stories prioritized over P1/P2/P3"},{"sprint_plan_generated":"Sprint plan file created with goals, stories, risks, and metrics"}]
inputs
{"sprint_name":{"type":"string","required":true,"description":"Name of sprint (e.g., 'Sprint 1', 'Q1 Sprint 3')"},"velocity":{"type":"number","required":true,"description":"Team velocity in story points (historical or estimated)"},"plan_ahead":{"type":"number","default":1,"description":"Number of sprints to plan (1-4)"},"stories":{"type":"array","required":false,"description":"Specific story IDs to include (default: auto-select from backlog)"},"buffer":{"type":"number","default":0.15,"description":"Reserve buffer percentage (default: 15% of velocity)"}}
outputs
{"sprint_plan":{"type":"object","description":"Sprint plan with goals, stories, capacity, risks"},"commitment":{"type":"number","description":"Total story points committed"},"utilization":{"type":"number","description":"Percentage of velocity utilized"},"sprint_plan_file":{"type":"string","description":"Path to generated sprint plan file"}}
Create comprehensive sprint plans by intelligently grouping estimated user stories based on team velocity, dependencies, priorities, and risk mitigation.
Purpose
Transform backlog of estimated stories into actionable sprint commitments:
Calculate effective capacity (velocity - buffer)
Select stories respecting dependencies and priorities
Balance workload and minimize risk
Generate sprint plan with goals, metrics, and risk mitigation
Support multi-sprint planning (roadmap view)
When to Use This Skill
This skill should be used when:
Starting a new sprint (during Sprint Planning ceremony)
Re-planning mid-sprint due to significant changes
Creating multi-sprint roadmap (2-4 sprints ahead)
Evaluating sprint capacity and feasibility
Balancing team workload across multiple teams
This skill should NOT be used when:
Stories are not yet estimated (use estimate-stories first)
[Action Verb] [Feature/Outcome] so that [Business Value]
Examples:
"Implement core authentication so that users can securely access the platform"
"Enable user profile management so that users can personalize their experience"
"Complete payment integration so that customers can purchase products"
Good Sprint Goals:
Specific: Clear what will be delivered
Measurable: Can verify if goal achieved
Valuable: Business value is clear
Achievable: Realistic given velocity
Focused: 1-2 main themes, not scattered
Poor Sprint Goals:
❌ "Complete as many stories as possible"
❌ "Work on authentication and profiles and settings and..."
❌ "Make progress on the backlog"
Output: Sprint goal defined following formula ([Action] [Feature] so that [Business Value]), success criteria specified, goal validated (specific/measurable/valuable/achievable/focused)
See:references/templates.md#step-5-output for complete goal examples and sprint-goals-and-metrics.md for goal patterns
Step 6: Calculate Sprint Metrics
Purpose: Provide quantitative sprint health indicators.
Output: Sprint plan document generated with sections: Sprint Goal, Committed Stories table, Sprint Metrics, Risks and Mitigation, Sprint Schedule, Definition of Done
File:.claude/sprints/sprint-{name}-{date}.md
See:references/templates.md#step-7-output for complete sprint plan document template with all sections
Step 8: Multi-Sprint Planning (Optional)
Purpose: Plan 2-4 sprints ahead for roadmap visibility.
When to Use:
plan_ahead parameter > 1
Creating quarterly roadmap
Long-range feature planning
Process:
Plan Sprint 1 (as above)
Mark Sprint 1 stories as "allocated"
Repeat Steps 1-7 for Sprint 2 with remaining stories
Continue for Sprint 3, 4 as needed
Output: Multiple sprint plans generated, total roadmap points, stories distributed across sprints, files created for each sprint
See:references/templates.md#step-8-output for multi-sprint roadmap example and sprint-planning-mechanics.md for algorithm
Step 9: Present Sprint Plan Summary
Purpose: Communicate sprint plan clearly to team.
Output: Sprint plan summary with sprint name/dates, commitment details (stories/points/utilization), sprint goal, top stories list, risk summary, sprint plan file path, next steps
See:references/templates.md#step-9-output for complete summary format
Integration with Other Skills
Before Sprint Planning:
breakdown-epic → Create stories from epics
refine-story → Ensure stories are sprint-ready
estimate-stories → Estimate story points
After Sprint Planning:
implement-feature → Implement stories from sprint
review-task → Quality check completed stories
(Next sprint) → sprint-plan again with updated velocity
Best Practices
Respect velocity (10-15% buffer) | Honor dependencies (never break chains) | Focus on value (P0/P1 first) | Balance risk (mix high/low risk stories) | Complete features (avoid half-done work) | Review and adapt (update velocity based on actuals)
See:sprint-goals-and-metrics.md for detailed planning best practices
Reference Files
Detailed documentation in references/:
templates.md: All output formats (Steps 0-9), complete sprint plan document template, multi-sprint roadmap examples, risk assessment examples, sprint goal examples, JSON output format