What problem does it solve? Teams chronically over-commit because they treat velocity as a single flattering number instead of an honest distribution. This Skill provides the per-preset capacity math needed to answer how much work a team can actually take on, so sprint commits, cycle appetites, kanban WIP limits, and phased release scope are grounded in real signals rather than optimistic point estimates. ## Core Features & Use Cases - Per-Preset Capacity Math: Reads velocity as a distribution under sprint, appetite as a budget under cycle, WIP limits plus card aging under kanban, and gate-by-gate release scope under phased. - Story Queue Cut-Line: Walks a priority-sorted queue, sums against capacity, promotes dependencies, and draws a non-negotiable cut-line separating proposed-in from proposed-out work. - Anti-Pattern Detection: Flags sandbagging, headline velocity numbers that erase distributions, WIP limits raised to hide bottlenecks, and appetite treated as an estimate. - Use Case: A team with sprint velocities of 28, 41, 19, 35, 30, 33 wants to commit next sprint. The Skill plans the commit against the median of 31.5 rather than last sprint's 35, sums the sorted queue to 29 points, and places the cut-line so remaining stories become forecast, not promise. ## Quick Start Ask the capacity planner to read our last six sprints of velocity and draw the cut-line on the prioritized Story Queue for the next sprint commit.
