Hotfix Flow
Drive an expedited production hotfix from red to green: reproduce the live defect with a failing test, apply the smallest safe fix that makes it pass without scope-creeping into a refactor, and verify the fix plus a clean regression check before it ships out-of-band. The ordering is the whole discipline — reproduce FIRST (a failing test that captures the bug is the contract the fix must satisfy), then fix minimally, then verify the new test passes and nothing else broke. Use this for urgent production bugs, expedited patch releases, and out-of-band fixes where speed matters but a regression would be worse than the original bug.
How it runs
| # | Step | Who runs it | What happens |
|---|---|---|---|
| 1 | Reproduce with a failing test | Developer | capture the live defect as a failing, deterministic test |
| 2 | Apply the minimal fix | Developer | smallest safe change that turns the failing test green |
| 3 | Verify and regression-check | Reviewer | confirm green plus no regressions before shipping |
| 4 | Evaluate | Reviewer | Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap. |
| 5 | Finish | Developer | All acceptance criteria met. Stamp a short summary and report DONE. |
Say something like "hotfix this bug" or "urgent production fix" or "expedited patch" or "fix the live defect" or "out-of-band fix" in chat to start it.