parallel-debugging
Parallel Debugging applies the Analysis of Competing Hypotheses methodology to organize multi-agent investigation of complex issues. It structures hypothesis generation across six failure mode categories, establishes evidence collection standards with citation requirements, and provides arbitration protocols to identify root causes while avoiding confirmation bias.
Parallel Debugging helps you systematically investigate complex bugs with multiple potential causes using competing hypotheses methodology.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-22
Parallel Debugging helps you systematically investigate complex bugs with multiple potential causes using competing hypotheses methodology. Parallel Debugging applies the Analysis of Competing Hypotheses methodology to organize multi-agent investigation of complex issues. It structures hypothesis generation across six failure mode categories, establishes evidence collection standards with citation requirements, and provides arbitration protocols to identify root causes while avoiding confirmation bias.
Use it when
- Parallel Debugging applies the Analysis of Competing Hypotheses (ACH) methodology to structure root cause analysis.
- Parallel Debugging enforces evidence collection standards with citation requirements and competing hypotheses analysis.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
wshobson/agents/parallel-debugging · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I debug complex bugs that span multiple modules?
Parallel Debugging organizes investigation across multiple components by structuring hypothesis generation across six failure mode categories and establishing parallel investigation workflows. This approach lets you systematically explore different potential causes simultaneously rather than pursuing a single theory, reducing the risk of missing the actual root cause when bugs involve interactions between modules.
What is the competing hypotheses methodology for bug investigation?
Parallel Debugging applies the Analysis of Competing Hypotheses (ACH) methodology to structure root cause analysis. Instead of confirming a single theory, ACH requires you to generate multiple plausible explanations, collect evidence against each one, and use structured arbitration to identify which hypothesis is most consistent with your findings. This prevents confirmation bias by forcing systematic evaluation of alternatives.
How does parallel-debugging help avoid confirmation bias when debugging?
Parallel Debugging enforces evidence collection standards with citation requirements and competing hypotheses analysis. By requiring you to actively seek disconfirming evidence and evaluate multiple root causes in parallel rather than fixating on one theory, the framework prevents the natural tendency to interpret findings as support for your initial assumption. Confidence scoring helps arbitrate between plausible causes objectively.
What is a systematic debugging framework for hard-to-find bugs?
Parallel Debugging provides a structured root cause analysis framework that combines hypothesis generation across failure mode categories, evidence-based investigation with citation standards, and competing hypotheses methodology. This systematic approach organizes complex debugging workflows, establishes clear protocols for arbitrating between multiple plausible causes, and ensures you collect sufficient evidence before concluding what actually caused the issue.
How do I find the root cause of complex bugs with multiple potential causes?
Parallel Debugging structures root cause analysis by generating competing hypotheses across six failure mode categories, collecting evidence with citation requirements, and applying arbitration protocols with confidence scoring. This evidence-based methodology helps you systematically evaluate each potential cause, identify which explanations are most consistent with your findings, and avoid settling on an incorrect root cause prematurely.
What debugging methodology uses competing hypotheses and parallel investigation?
Parallel Debugging applies the Analysis of Competing Hypotheses (ACH) method to organize multi-agent investigation of complex issues. It structures hypothesis generation, establishes evidence collection standards, and provides arbitration protocols to identify root causes while avoiding confirmation bias. The framework is designed specifically for bugs with multiple potential causes across different components or modules.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Parallel Debugging
Framework for debugging complex issues using the Analysis of Competing Hypotheses (ACH) methodology with parallel agent investigation.
When to Use This Skill
- Bug has multiple plausible root causes
- Initial debugging attempts haven't identified the issue
- Issue spans multiple modules or components
- Need systematic root cause analysis with evidence
- Want to avoid confirmation bias in debugging
Hypothesis Generation Framework
Generate hypotheses across 6 failure mode categories:
1. Logic Error
- Incorrect conditional logic (wrong operator, missing case)
- Off-by-one errors in loops or array access
- Missing edge case handling
- Incorrect algorithm implementation
2. Data Issue
- Invalid or unexpected input data
- Type mismatch or coercion error
- Null/undefined/None where value expected
- Encoding or
(truncated - see the full file via the links below)
File tree — 2 files
plugins/agent-teams/skills/parallel-debugging/SKILL.md
plugins/agent-teams/skills/parallel-debugging/references/hypothesis-testing.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Debug complex bugs with multiple potential causes using systematic methodology”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Trace systematically investigates why something happened by generating competing hypotheses and evaluating evidence for and against each one. It's built for ambiguous causal questions—runtime bugs, performance regressions, and architecture issues—where you need to explain the most likely explanation. The skill structures your investigation through observation, hypothesis generation, evidence gathering, and discriminating probes.
This skill systematically investigates why problems occur by separating genuine causal relationships from correlations and symptoms. It guides you through defining effects, generating competing hypotheses, building causal models, testing causality rigorously, and documenting findings with confidence levels. Apply it to incident investigations, metric changes, policy evaluation, or debugging.
Investigate walks you through a structured methodology to pinpoint what's causing bugs, test failures, build errors, and unexpected behavior. It cycles through characterization, isolation, hypothesis generation, and targeted testing—with escalation to deeper analysis when needed—to diagnose the root cause without applying fixes.
Bug Hunt Swarm deploys four read-only sub-agents in parallel to investigate bugs, regressions, and crashes from different angles—reproduction scope, code paths, recent changes, and proof strategies. The main agent then synthesizes findings into ranked hypotheses with supporting evidence and the fastest path to confirm or disprove each theory, all without making code edits.
Debug helps you trace application issues methodically from symptom to root cause using structured log analysis, error parsing, and hypothesis testing. It enforces a disciplined four-phase workflow: investigate the error completely, analyze patterns in working code, form and test a single hypothesis, then implement the fix—preventing the common trap of patching symptoms instead of solving underlying problems.
Debug Investigator replaces ad-hoc troubleshooting with structured investigation: capture symptoms, build a reproducible feedback loop, analyze evidence from stacktraces and logs, generate ranked hypotheses, and design bisection strategies. Use it for non-obvious bugs—intermittent failures, performance regressions, or issues requiring systematic root cause analysis—where native debugging falls short.
More skills Systematic Debugging (unlicensed) · systematic-debugging (MIT)