Bug Fix Brief

This generates a standardized Bug Fix Brief document in your docs/bfb/ folder whenever you need to properly document a bug correction. It walks you through the essentials: repro steps, root cause down to the file and line number, at least two fix options with a decision rationale, and a verification checklist. The structure is opinionated but lightweight, which is the point. It keeps sequential numbering, forces you to compare alternatives before committing to a fix, and makes sure every bug gets the same treatment whether it's a null pointer or a race condition. Good for teams that want fix documentation without the ceremony of a full postmortem process.