parallel-debugging

Automates parallel hypothesis generation, evidence collection, and arbitration for complex debugging tasks.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill parallel-debugging-ekremmkasap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-debugging
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/agent-teams/skills/parallel-debugging
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill parallel-debugging-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debug complex issues by providing a structured ACH-based framework to generate competing hypotheses, collect evidence, and arbitrate root causes.

Core Features & Use Cases

  • Hypothesis generation across multiple failure modes (logic, data, state, integration, resources, environment)
  • Evidence collection standards and formal reporting templates
  • Arbitration workflow to determine root causes and guide fixes

Quick Start

Describe a bug and instruct the system to begin parallel hypothesis analysis.

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 multi-cause bugs spanning multiple modules?

Debug complex multi-cause bugs using an ACH-based framework that automates parallel hypothesis generation, evidence collection, and root-cause arbitration. This structured approach systematically investigates logic, data, state, and integration failure modes.

What is the best way to investigate race conditions and integration failures?

Investigate race conditions and integration failures by running parallel competing hypotheses through a structured arbitration protocol. This method evaluates evidence against multiple potential causes simultaneously to isolate the root cause.

How does root-cause analysis work with parallel hypotheses?

Root-cause analysis with parallel hypotheses works by generating competing scenarios across different failure modes, collecting standardized evidence, and applying an arbitration workflow. A decision tree then arbitrates the collected evidence to determine the actual root cause.

Can I use this ACH-based debugging framework for environment and resource failures?

Yes, you can use this ACH-based debugging framework for environment and resource failures. Hypothesis generation explicitly covers multiple failure modes including logic, data, state, integration, resources, and environment for comprehensive coverage.

How do I start structured debugging for a complex bug?

Start structured debugging for a complex bug by describing the issue and instructing the system to begin parallel hypothesis analysis. The framework then generates hypotheses, applies evidence collection standards, and produces formal reproducible reports.

When should I avoid using parallel hypothesis testing for debugging?

Avoid using parallel hypothesis testing for simple, single-cause bugs where the root cause is already obvious. This structured arbitration framework is designed specifically for complex, multi-cause issues requiring systematic evidence evaluation and decision trees.