What problem does it solve? Teams running sprints routinely over-commit, treat velocity as a single number, and let plans drift into fiction by mid-week. This Skill provides the mechanics for honest sprint planning: reading velocity as a distribution, splitting commit from stretch, drawing a defensible cut-line on the story queue, and replanning when reality drifts. ## Core Features & Use Cases - Velocity Distribution Analysis: Plan commits against the median of recent sprints rather than a point estimate, reserving room for variance. - Commit vs Stretch Splitting: Separate the public stakeholder promise (commit) from opportunistic work (stretch) so misses are meaningful and sandbagging is visible. - Cut-Line and Drift Management: Walk the prioritized story queue, promote dependencies, enforce that unsized stories return to refinement, and use standup plus a day-3 check-in as replanning surfaces. - Use Case: A PM planning a two-week sprint reviews the last six velocities (28, 41, 19, 35, 30, 33), commits to 29 points of refined stories, holds 10 points as stretch, and drops a story explicitly when a production incident eats capacity on day 3. ## Quick Start Ask the AI to help plan the upcoming sprint using the team's recent velocity history and the prioritized queue of ready stories.
