root-cause-investigator

To find the root cause of a build failure, apply a structured 5-Why investigation by gathering initial context and iteratively asking why to drill down through symptoms and evidence to the underlying issue.

The 5-Why methodology for software debugging is a systematic investigation technique that iteratively asks 'why' to drill down through symptoms, processes, and architecture until the fundamental root cause is identified and documented.

To systematically troubleshoot performance degradation or integration issues, gather initial context and relevant logs, then perform an iterative 5-Why analysis to document evidence across affected systems and identify the root cause.

Yes, you can use this 5-Why analysis for diagnosing test failures across software systems. The methodology applies broadly to errors, build failures, performance issues, and integration problems without requiring specific platform dependencies.

To start a root-cause investigation, you need to provide an initial issue description and relevant logs. The investigation workflow then uses this context to systematically identify, analyze, and document the root cause.