parallel-debugging

Parallel debugging of multi-service issues requires structured evidence arbitration. This skill applies Analysis of Competing Hypotheses (ACH) to generate hypotheses across six failure mode categories, coordinate parallel investigations, and use an arbitration decision tree to isolate the dominant root cause.

Organizing competing hypotheses for root-cause analysis involves categorizing them into failure modes like Logic Error, Data Issue, or Integration Failure. This skill provides templates for formal hypothesis testing and a structured arbitration workflow to evaluate evidence against each hypothesis.

Structuring evidence collection for parallel investigations requires citation-ready reporting formats. This skill applies formal Evidence Report templates to guide data gathering across multiple components, ensuring each piece of evidence is formally mapped to specific debugging hypotheses for accurate arbitration.

Yes, debugging integration failures in multi-component architectures is fully supported. The skill specifically categorizes Integration Failure as one of its six hypothesis modes, enabling teams to systematically explore cross-module dependencies and document findings for safer releases.

You need a formal arbitration decision tree for debugging when bugs span several modules and generate conflicting evidence. It helps categorize investigation results, determine a single dominant root cause from competing hypotheses, and validate fixes before deployment.