debug-like-expert

Systematic debugging uses rigorous evidence gathering and hypothesis testing to isolate root causes. It provides a structured framework to methodically investigate complex issues without making premature code changes.

To debug a complex system failure, apply a defensive mindset by capturing state and inputs, generating testable hypotheses, and designing minimal experiments for controlled verification until the root cause is isolated.

Use hypothesis-driven debugging when standard troubleshooting fails or issues require rigorous, repeatable analysis across teams. It prevents premature code changes by enforcing evidence gathering and controlled verification first.

The best way to document evidence gathering is using structured templates to capture state, inputs, and outcomes, documenting every investigative step to produce explainable conclusions and actionable remediation.

To design minimal experiments for verification-oriented debugging, generate testable hypotheses from gathered evidence, then apply controlled verification to reason about causes and plan fixes with clear acceptance criteria.