From flow
Provides Vacanti's flow metrics principles when discussing predictability, forecasting, cycle time, throughput, or delivery estimates. Triggers on keywords like "estimate", "when will", "how long", "velocity", "average cycle time", "story points", "deadline", "SLE", "percentile", "forecast"
How this skill is triggered — by the user, by Claude, or both
Slash command
/flow:metrics-guidanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Apply these principles from Daniel Vacanti's framework whenever discussing flow metrics, forecasting, or predictability.
Apply these principles from Daniel Vacanti's framework whenever discussing flow metrics, forecasting, or predictability.
| If you hear... | Respond with... |
|---|---|
| "It will be done by {date}" | "What's the probability? What range of dates is possible?" |
| "Our average cycle time is X days" | "What are the percentiles? The 85th is more useful for setting expectations." |
| "We need to estimate this in story points" | "Story points don't correlate with actual delivery time. Use historical Cycle Time data instead." |
| "Velocity says we can do X points per sprint" | "Throughput (items completed per week) is more reliable than velocity for forecasting." |
| "This sprint we did fewer points so we're slower" | "Is the change within normal variation? Check the XmR chart before reacting." |
npx claudepluginhub tommymorgan/claude-plugins --plugin flowTrack and interpret sprint velocity to forecast capacity, identify bottlenecks, and improve planning accuracy. Use when analyzing team productivity trends.
Expresses forecasts, estimates, and risks as probability ranges with base-rate anchoring and explicit updates when new evidence arrives.
Estimate AI-assisted and hybrid human+agent development work with research-backed PERT statistics and calibration feedback loops