What problem does it solve? Debugging issues with multiple plausible root causes often leads to confirmation bias and wasted effort chasing a single theory. This Skill structures root cause analysis using the Analysis of Competing Hypotheses (ACH) methodology, coordinating parallel investigations with rigorous evidence standards. ## Core Features & Use Cases - Hypothesis Generation Framework: Systematically generates hypotheses across six failure mode categories: logic errors, data issues, state problems, integration failures, resource issues, and environment differences. - Evidence Collection Standards: Classifies evidence by strength (direct, correlational, testimonial, absence) with mandatory file:line citations and calibrated confidence levels. - Result Arbitration Protocol: Categorizes findings as confirmed, plausible, falsified, or inconclusive, then ranks competing hypotheses to determine the root cause. - Use Case: When a production API intermittently returns 500 errors, spawn parallel investigations into handler exceptions, database connections, and environment variables, then arbitrate the evidence to identify the true root cause. ## Quick Start Use the parallel-debugging skill to investigate why the checkout endpoint intermittently fails by generating competing hypotheses and collecting evidence for each.
