parallel-debugging

Generate competing hypotheses and collect evidence to identify root causes.

3|2|Updated Mar 23, 2026

Search Tags:#debugging #evidence #root-cause #arbitration #hypotheses #parallel-investigation #ach

Ready to run

npx skills add https://github.com/wesleyegberto/software-engineering-skills --skill parallel-debugging-wesleyegberto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: parallel-debugging
Source: https://github.com/wesleyegberto/software-engineering-skills/tree/main/plugins/programming-skills/skills/parallel-debugging
Command: npx skills add https://github.com/wesleyegberto/software-engineering-skills --skill parallel-debugging-wesleyegberto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Parallel debugging with competing hypotheses organizing investigations when bugs have multiple plausible root causes; ensures a systematic, evidence-driven approach to arbitration of root causes across modules and environments.

Core Features & Use Cases

ACH-based hypothesis management to generate, compare, and prune competing explanations
Evidence collection with structured citations to support or refute hypotheses
Arbitration workflow to determine root cause and guide corrective actions
Reproducible templates for end-to-end debugging sessions across services

Quick Start

Provide a structured ACH-based plan for diagnosing a multi-service bug by listing competing hypotheses and the required evidence to collect

Frequently Asked Questions about parallel-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug complex bugs spanning multiple modules or services?▼

Debugging multi-service bugs requires coordinating parallel investigations by generating competing hypotheses, collecting evidence with file references, and systematically arbitrating the root cause. This approach applies ACH methodology to ensure an evidence-driven decision process.

What is ACH methodology for root-cause analysis?▼

ACH (Analysis of Competing Hypotheses) methodology generates competing explanations, compares them against collected evidence, and prunes refuted options to determine the root cause. It structures complex debugging into a reproducible, evidence-driven arbitration workflow.

How do I structure parallel investigations when debugging multi-service issues?▼

Structure parallel debugging by listing competing hypotheses and mapping required evidence collection to each. Use ACH-based templates to document file references and systematically arbitrate root causes across the involved modules and environments.

Does this approach work for bugs with multiple plausible root causes?▼

Yes, this approach specifically targets bugs with multiple plausible root causes. It applies ACH-based hypothesis management to generate, compare, and prune competing explanations, ensuring systematic arbitration across modules and environments.

What's the best way to document evidence during a root-cause analysis?▼

Document evidence during root-cause analysis using structured citations with file references. Collect direct and correlational evidence to support or refute specific hypotheses, ensuring the debugging decision process remains fully reproducible.

When should I use competing hypotheses for debugging?▼

Use competing hypotheses when a complex bug spans multiple modules, services, or environments and has multiple plausible root causes. This ACH-based approach ensures systematic evidence collection and arbitration rather than relying on singular assumptions.