systematic-debugging

Root cause analysis for intermittent production failures requires systematically capturing full error outputs, reproducing the failure consistently, and tracing data flow across boundaries to pinpoint the exact defect.

Debugging a failing test after a commit requires capturing the full error output, reproducing the failure consistently, and following a phase-guided workflow of pattern analysis and hypothesis testing to identify the root cause before proposing a fix.

Tracing data flow to fix a bug follows a phase-guided workflow: capture errors, reproduce the failure, analyze patterns, test hypotheses, and implement a minimal verified fix while tracking observability and state snapshots at boundaries.

You should escalate an intermittent failure after three failed debugging attempts, leveraging the built-in escalation guardrails to maintain a clear documentation trail and hand off the data-flow tracing investigation.

This workflow requires clear error messages, access to recent code changes, and a defined boundary plan to effectively trace data flow across development, CI, and production environments.

To ensure a minimal and verified fix, follow the structured debugging phases of hypothesis testing and implementation, using checkpoints and boundary data flow tracing to verify the root cause is resolved without introducing changes.