Bug Hunt

A hunt that leaves a trail. Most debugging loses its own history: three hypotheses get tried, two are silently abandoned, the fix lands, and the next person — or the next session — starts from zero and retries the abandoned two.

This workflow keeps the trail. Every hypothesis is written down with the observation that would kill it and the observation that actually came back. Falsified hypotheses stay in the record. The fix is pinned by a check that failed for the defect's reason before it passed.

The artifact is .bug-hunts/<YYYY-MM-DD>-<slug>.md. Create it at step 1 and keep writing to it as you go — a record written at the end is a summary, not a trail.

1. State the defect as an observation

Write, into the record: