/competing-hypothesis-construction
Strategy: Construct multiple competing hypotheses for the same phenomenon
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill competing-hypothesis-construction --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/competing-hypothesis-construction
Context preview
The summary Claude sees to decide when to auto-load this skill.
Strategy: Construct multiple competing hypotheses for the same phenomenon
SKILL.md
competing-hypothesis-construction.SKILL.mdname: competing-hypothesis-construction
description: 'Strategy: Construct multiple competing hypotheses for the same phenomenon'
version: 1.0.0
category: hypothesis-formation
type: strategy
campaign: hypothesis-formulation
tactics:
- competing-hypothesis-matrix
sops:
- competing-hypothesis-generation
- discriminating-prediction-design
- hypothesis-comparison-matrix
- falsifiability-check
dependencies:
tactics:
- competing-hypothesis-matrix
sops:
- falsifiability-check
Competing Hypothesis Construction
Construct multiple competing hypotheses for the same phenomenon: actively counter confirmation bias, maintain epistemic openness by building genuinely different explanations in parallel, and design decisive predictions that can distinguish them.
When to Use
- The researcher already has a "preferred hypothesis" and needs to actively challenge it
- The phenomenon has multiple plausible explanations, and premature convergence would lead in the wrong direction
- You need to show reviewers or funders that alternative explanations have been considered
- When designing experiments, you need to determine which variable best discriminates between competing explanations
Not applicable: the phenomenon has overwhelming evidence supporting a single explanation → directly use deductive-hypothesis-generation to refine that explanation.
Thinking Framework
**Avoid confirmation bias by generating genuinely different explanations, then find discriminating predictions**
The core logic of competing hypothesis construction:
1. **Force diversity**: competing hypotheses must be genuinely different at the mechanism level, not variants of the same mechanism 2. **Symmetric treatment**: each hypothesis is treated with equal seriousness; the preferred hypothesis is not allowed special treatment 3. **Discriminating predictions**: find decisive predictions that distinguish the hypotheses — what result supports H1 but contradicts H2, and vice versa 4. **Matrix comparison**: reveal structural differences between hypotheses through a systematic matrix
**Quality criteria for competing hypotheses**:
- **Genuinely competing**: two hypotheses give different causal explanations for the same phenomenon (not weaker/stronger versions of the same explanation)
- **Mutual exclusivity**: there exists at least one observable result that can support one while contradicting the other
- **Comparability**: both hypotheses have clear testable predictions
Budget Gate
| Tier | Competing hypotheses | Discriminating predictions | Comparison matrix | Falsifiability | |------|---------|---------|---------|---------| | S | ≥2 genuinely competing hypotheses | ≥1 discriminating prediction | simplified version (2×2) | 1 falsification scenario per hypothesis | | M | ≥3 competing hypotheses | ≥2 discriminating predictions | full matrix (hypotheses × predictions) | full falsification per hypothesis | | L | ≥4 competing hypotheses | ≥3 discriminating predictions | full matrix + experiment design suggestions | full falsifiability audit |
Default Reference Flow
1. Call the `competing-hypothesis-generation` SOP (via the `competing-hypothesis-matrix` tactic): force generation of hypotheses that are genuinely different at the mechanism level 2. Call the `discriminating-prediction-design` SOP: design discriminating predictions for each pair of competing hypotheses 3. Call the `hypothesis-comparison-matrix` SOP: build a hypotheses × predictions comparison matrix to reveal structural differences 4. Call the `falsifiability-check` SOP: generate a falsification scenario for each hypothesis
context-checkpoint
Record after each round:
- Competing hypothesis list (core mechanism statement for each hypothesis)
- Mechanism difference analysis (at what level the hypotheses are genuinely different)
- Discriminating prediction list (which pair of hypotheses each prediction can distinguish)
- Comparison matrix (hypotheses × predictions, annotated support/contradict/neutral)
- Recommended decisive experiment directions
<!-- BEGIN available-tables (generated) -->
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | competing-hypothesis-matrix | Tactic: Multi-hypothesis management — generate competing hypotheses, design discriminating predictions, build a structured comparison matrix |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | falsifiability-check | SOP: check whether a hypothesis meets the falsifiability criterion |
<!-- END available-tables (generated) -->
Read more
name: competing-hypothesis-construction description: 'Strategy: Construct multiple competing hypotheses for the same phenomenon' version: 1.0.0 category: hypothesis-formation type: strategy campaign: hypothesis-formulation tactics: - competing-hypothesis-matrix sops: - competing-hypothesis-generation - discriminating-prediction-design - hypothesis-comparison-matrix - falsifiability-check dependencies: tactics: - competing-hypothesis-matrix sops: - falsifiability-check
Competing Hypothesis Construction
Construct multiple competing hypotheses for the same phenomenon: actively counter confirmation bias, maintain epistemic openness by building genuinely different explanations in parallel, and design decisive predictions that can distinguish them.
When to Use
- The researcher already has a "preferred hypothesis" and needs to actively challenge it
- The phenomenon has multiple plausible explanations, and premature convergence would lead in the wrong direction
- You need to show reviewers or funders that alternative explanations have been considered
- When designing experiments, you need to determine which variable best discriminates between competing explanations
Not applicable: the phenomenon has overwhelming evidence supporting a single explanation → directly use deductive-hypothesis-generation to refine that explanation.
Thinking Framework
**Avoid confirmation bias by generating genuinely different explanations, then find discriminating predictions**
The core logic of competing hypothesis construction:
1. **Force diversity**: competing hypotheses must be genuinely different at the mechanism level, not variants of the same mechanism 2. **Symmetric treatment**: each hypothesis is treated with equal seriousness; the preferred hypothesis is not allowed special treatment 3. **Discriminating predictions**: find decisive predictions that distinguish the hypotheses — what result supports H1 but contradicts H2, and vice versa 4. **Matrix comparison**: reveal structural differences between hypotheses through a systematic matrix
**Quality criteria for competing hypotheses**:
- **Genuinely competing**: two hypotheses give different causal explanations for the same phenomenon (not weaker/stronger versions of the same explanation)
- **Mutual exclusivity**: there exists at least one observable result that can support one while contradicting the other
- **Comparability**: both hypotheses have clear testable predictions
Budget Gate
| Tier | Competing hypotheses | Discriminating predictions | Comparison matrix | Falsifiability | |------|---------|---------|---------|---------| | S | ≥2 genuinely competing hypotheses | ≥1 discriminating prediction | simplified version (2×2) | 1 falsification scenario per hypothesis | | M | ≥3 competing hypotheses | ≥2 discriminating predictions | full matrix (hypotheses × predictions) | full falsification per hypothesis | | L | ≥4 competing hypotheses | ≥3 discriminating predictions | full matrix + experiment design suggestions | full falsifiability audit |
Default Reference Flow
1. Call the `competing-hypothesis-generation` SOP (via the `competing-hypothesis-matrix` tactic): force generation of hypotheses that are genuinely different at the mechanism level 2. Call the `discriminating-prediction-design` SOP: design discriminating predictions for each pair of competing hypotheses 3. Call the `hypothesis-comparison-matrix` SOP: build a hypotheses × predictions comparison matrix to reveal structural differences 4. Call the `falsifiability-check` SOP: generate a falsification scenario for each hypothesis
context-checkpoint
Record after each round:
- Competing hypothesis list (core mechanism statement for each hypothesis)
- Mechanism difference analysis (at what level the hypotheses are genuinely different)
- Discriminating prediction list (which pair of hypotheses each prediction can distinguish)
- Comparison matrix (hypotheses × predictions, annotated support/contradict/neutral)
- Recommended decisive experiment directions
<!-- BEGIN available-tables (generated) -->
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | competing-hypothesis-matrix | Tactic: Multi-hypothesis management — generate competing hypotheses, design discriminating predictions, build a structured comparison matrix |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | falsifiability-check | SOP: check whether a hypothesis meets the falsifiability criterion |
<!-- END available-tables (generated) -->
The complete research orchestration system for AI-native science. What It Does Design Philosophy Architecture (v3.2.2) Quick Start Configuration Roadmap License DARE is not a tool that helps you do research. It is the researcher.
Repo: yogsoth-ai/de-anthropocentric-research-engine
Other skills on de-anthropocentric-research-engine.
- /formated-results
Closing skill for the research-executor, loaded as the last step of formated-specs. Summarize the design just produced into one research-result JSON fenced block in your reply. Do not execute the research.
Open skill - /formated-specs
Spec-slot skill for the research-executor. Emit the 4-layer DARE orchestration of the assigned topic as one research-graph JSON fenced block in your reply. Replaces the generic spec-writing step.
Open skill - /injection-fidelity
Loss-1 judge (codex role). Given one sample's de-identified dialogue and its PolicyCard, decide axis-by-axis whether the user-simulator enacted the card's per-axis pressure. Judge enactment of the card, never whether the research is good.
Open skill - /ladder-quality-order
Loss-2 judge (codex role). Over one topic's 6 shuffled research-design samples, pairwise-rank by quality using the D1–D5 standard. Emit the pairwise log; the harness computes the order and the ladder verdicts. Judge quality difference, never against academic standards.
Open skill - /optimization-loop
The optimizer brain for the ladder-foundry pretraining loop. Runs the two-level nested batch loop, delegates gating to gate_eval, attributes a failing batch to one weight (attribute-first), and recovers from disk after compaction. Control flow is fully scripted; only the
Open skill - /acu-nugget-recall
Tactic: Extract atomic units from one paper and score how much of a caller-supplied summary covers. Use for ACU-style binary or Nugget-style ternary recall checks; cannot run without a target summary.
Open skill

