investigate

A root cause analysis for software systems requires gathering evidence and testing hypotheses systematically. This skill guides a four-phase workflow—investigate, analyze, hypothesize, implement—using tools like grep and web search to isolate the underlying issue before any fixes are applied.

The best way to debug flaky behavior across services is following a structured investigation workflow that enforces the rule of no fixes without root cause. It proactively prompts you to identify symptoms, gather evidence, and test hypotheses across your codebase to isolate the problem.

To start root cause analysis during incident troubleshooting, provide a reproducible debugging scenario to initiate the structured four-phase plan. The workflow uses prompt-driven tools to collect information, identify symptoms, and guide you toward proposing fixes.

No, you cannot use this approach to fix performance regressions without finding the root cause. The workflow enforces an iron law of no fixes without root cause, ensuring you must isolate the underlying issue through evidence gathering and hypothesis testing before implementing any changes.

A structured debugging workflow isolates issues in software systems by guiding you through four phases: investigate, analyze, hypothesize, and implement. It integrates tools like grep, web search, and user questions to collect evidence and test hypotheses against the observed symptoms.