菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/adolfoaranaes12/BMAD-ENHANCED --skill sprint-plan命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Comprehensive brownfield architecture analysis for existing codebases. Discovers structure, identifies patterns, assesses quality, calculates production readiness, and provides actionable recommendations. Use when analyzing existing codebases to understand architecture, assess quality, or prepare for modernization.
Systematically consume QA quality gate outputs and apply prioritized fixes for high-severity issues, NFR failures, and test coverage gaps. Use when quality review identifies issues requiring remediation.
Peer review architecture for quality, risks, and optimization opportunities. Analyzes scalability bottlenecks, security vulnerabilities, performance optimization, technology fit, and provides prioritized recommendations. Use when reviewing proposed architecture documents for quality assurance, risk identification, or architectural decision validation.
基于 SOC 职业分类
正在显示 SKILL.md
| 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"}} |
| telemetry | {"emit":"skill.sprint-plan.completed","track":["sprint_name","velocity","duration_ms","stories_count","commitment_points","utilization_percent","p0_stories_count","dependencies_count"]} |
Create comprehensive sprint plans by intelligently grouping estimated user stories based on team velocity, dependencies, priorities, and risk mitigation.
Transform backlog of estimated stories into actionable sprint commitments:
This skill should be used when:
This skill should NOT be used when:
Execute steps in order - each builds on previous analysis:
Purpose: Gather all inputs needed for sprint planning.
Actions:
Validate sprint parameters:
Load all eligible stories from .claude/stories/:
Load dependencies:
Calculate effective capacity:
Effective Capacity = Velocity × (1 - Buffer)
Example: 20 points × (1 - 0.15) = 17 points available
Output: Sprint context loaded with velocity, buffer, effective capacity, eligible stories, dependencies identified
See: references/templates.md#step-0-output for complete format and sprint-planning-mechanics.md for capacity calculations
Purpose: Create prioritized list respecting business value and dependencies.
Sorting Criteria (in order):
Output: Stories prioritized and sorted by priority level, dependency order, risk score, story points
See: references/templates.md#step-1-output for complete sorted backlog example and story-selection-algorithm.md for sorting logic
Purpose: Fill sprint capacity with highest-value stories respecting constraints.
Selection Algorithm:
Output: Stories selected for sprint respecting capacity, dependencies, feature completeness | Total points, utilization percentage, remaining capacity
See: references/templates.md#step-2-output for complete selection example and story-selection-algorithm.md for selection rules
Purpose: Ensure no broken dependencies in sprint plan.
Validation Checks:
Blocker Check: All blocking stories either:
Feature Completeness: Avoid partial features:
Cross-Sprint Dependencies: For multi-sprint plans:
Output: Dependencies validated, all blocking relationships satisfied, no orphaned dependencies, feature completeness maintained
See: references/templates.md#step-3-output for complete validation examples including edge cases
Purpose: Surface sprint risks and plan mitigation.
Risk Categories:
Capacity Risk: Sprint over/under-committed
Dependency Risk: Critical path dependencies
Technical Risk: High-risk stories in sprint
Scope Risk: Too many P0 stories
Output: Sprint risks assessed by category (capacity/dependency/technical/scope), overall risk level, mitigation strategies identified
See: references/templates.md#step-4-output for detailed risk assessment example and sprint-risk-assessment.md for scoring methodology
Purpose: Articulate clear, measurable sprint goal.
Sprint Goal Formula:
[Action Verb] [Feature/Outcome] so that [Business Value]
Examples:
Good Sprint Goals:
Poor Sprint Goals:
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
Purpose: Provide quantitative sprint health indicators.
Key Metrics:
Output: Sprint metrics calculated including capacity (velocity/buffer/commitment/utilization), stories (total/priority breakdown), dependencies (relationships/longest chain), risk (average score/high-risk count/overall level)
See: references/templates.md#step-6-output for complete metrics example with all fields
Purpose: Create comprehensive sprint plan file.
File: .claude/sprints/sprint-{sprint-name}-{date}.md
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
Purpose: Plan 2-4 sprints ahead for roadmap visibility.
When to Use:
Process:
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
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
Before Sprint Planning:
breakdown-epic → Create stories from epicsrefine-story → Ensure stories are sprint-readyestimate-stories → Estimate story pointsAfter Sprint Planning:
implement-feature → Implement stories from sprintreview-task → Quality check completed storiessprint-plan again with updated velocityRespect 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
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
sprint-planning-mechanics.md: Capacity calculation, multi-sprint algorithm, velocity tracking
story-selection-algorithm.md: Sorting criteria, selection rules, edge cases
sprint-risk-assessment.md: Risk categories, scoring methodology, mitigation strategies
sprint-goals-and-metrics.md: Goal-setting patterns, metrics definitions, best practices