Systematic Debugging
Purpose
Make debugging reproducible and disciplined.
When to Use
Use for unclear failures, regressions, or unstable behavior.
Inputs
Symptoms, hypotheses, commands, code boundaries, observations.
Steps
- Write down hypotheses.
- Test one hypothesis at a time.
- Record the observation.
- Update the hypothesis list before changing direction.
Gates
Debugging has a clear trail of tested ideas and outcomes.
Evidence
Debug notes, command output, reduced repro, or identified culprit.
Anti-Patterns
Random edits, mixed hypotheses, and unrecorded attempts.
Related
debug-session, root-cause-tracing