Burndown Diagnosis
Diagnose a burndown or burnup from the user's own sprint, release, or project data plus team notes. Separates gross burn from scope change, fits velocity overall and recently, projects a finish with an explicit range, computes the velocity required to hit the date, classifies the curve pattern (flat then cliff, scope drift, steady shortfall, late batch landing, stale sizing), links each pattern to evidence in blockers, work in progress, carryover, and interruptions, and ends with ranked recovery options (cut scope, extend, add capacity, unblock, reduce work in progress) with trade-offs. Use when someone asks why we are behind, whether we will make the sprint or release date, what the burndown is telling us, how much scope to cut, or what the recovery options are. Do not use for turning raw standup updates into a summary (use standup-digest), for scoring risks (use risk-register), or for pricing a requested addition (use scope-change-brief).