competing-hypotheses

Coordinate parallel hypothesis testing to identify root causes of complex bugs.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/labrinyang/team-ochestractor --skill competing-hypotheses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competing-hypotheses
Source: https://github.com/labrinyang/team-ochestractor/tree/main/skills/competing-hypotheses
Command: npx skills add https://github.com/labrinyang/team-ochestractor --skill competing-hypotheses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When debugging unclear root causes with multiple plausible explanations, you need parallel investigation to converge on the correct issue faster.

Core Features & Use Cases

  • Phase-based investigation: forming hypotheses, parallel debugging, devil-advocate challenges, norming, verification, and recording learnings.
  • Team-based coordination: coordinator leads, multiple debuggers test hypotheses, and a mandatory devil-advocate to challenge all theories.
  • Real-world applicability: useful for enigmatic bugs, complex systems interactions, and regression avoidance by documenting conclusions.

Quick Start

Describe a bug, enumerate hypotheses, assign debuggers, and run parallel adversarial testing to converge on the root cause.

Frequently Asked Questions about competing-hypotheses

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

FAQPage Schema
How do I find a root cause when debugging complex systems with unclear failure modes?

Parallel debugging enables you to root out complex failure modes by testing multiple plausible explanations simultaneously. Assign debuggers to investigate different theories in parallel, applying devil-advocate constraints to eliminate incorrect paths and converge faster.

What is parallel hypothesis investigation for software debugging?

Parallel hypothesis investigation is a debugging technique where a coordinator assigns multiple debuggers to test different root-cause theories simultaneously. It includes mandatory devil-advocate challenges to disprove theories and documentation of evidence to confirm the final outcome.

How do I coordinate a team to debug an enigmatic bug with multiple plausible explanations?

Coordinate debugging an enigmatic bug by assigning a coordinator to lead multiple debuggers testing various hypotheses in parallel. Implement a mandatory devil-advocate role to challenge all theories, ensuring team psych-safety while documenting evidence and outcomes.

When should I use adversarial testing for root-cause analysis?

Use adversarial testing for root-cause analysis when facing enigmatic bugs or complex system interactions with unclear causes. Apply a devil-advocate approach to challenge parallel hypotheses, ensuring you verify the true failure mode and avoid regressions by recording learnings.

How do I avoid regression when fixing bugs with unclear root causes?

Avoid regression by documenting conclusions and evidence after parallel hypothesis testing. The investigation phases require recording learnings and outcomes from the devil-advocate verification process, ensuring the root cause is confirmed and future regressions are prevented.