Evidence-Driven Debugging

Overview

The active-debugging companion to investigate-root-cause. Where investigate produces a written hypothesis, evidence-driven-debugging is the workflow for testing that hypothesis with real instrumentation: logs, breakpoints, prints, debugger sessions, runtime probes. The skill exists because the most common debugging-phase failure is the engineer who runs through three or four mental hypotheses without writing anything down, ends up where they started, and can't reconstruct what they tried. Evidence-driven debugging keeps a paper trail. Used inside Phase 3 of investigate-root-cause, but invocable directly when an existing hypothesis just needs runtime testing.

When to Use