From thinking-framework-skills
Handles a by-name request for ACH (Analysis of Competing Hypotheses), the evidence-by-hypothesis disconfirmation matrix, honestly. Controlled trials found ACH raises confidence with no accuracy gain and does not reduce confirmation bias, so this skill does NOT build the matrix as if valid. It leads with that evidence, then routes to the evidence-based move the job actually needs (think-red-team-light, think-evidence-vs-inference-sort, or think-what-would-have-to-be-true). Use only when someone asks for ACH or a competing-hypotheses matrix by name.
How this skill is triggered — by the user, by Claude, or both
Slash command
/thinking-framework-skills:think-analysis-of-competing-hypothesesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- thinking-framework-skills | https://github.com/product-on-purpose/thinking-framework-skills | Apache-2.0 -->
ACH builds an evidence-by-hypothesis matrix, scores each item of evidence for how well it disconfirms each hypothesis, and favors the hypothesis with the least inconsistent evidence. It is a famous intelligence-analysis technique, and it was tested and found wanting: in randomized controlled studies it raised participants' confidence without improving accuracy, and showed no debiasing or judgment-quality gain. This skill therefore does not reproduce the matrix as if it were valid. It owns the request, leads with what the controlled evidence shows, and routes you to the evidence-based move your actual job needs. The output is an honest redirect brief, not a disconfirmation matrix with a declared winner.
ACH is tier X (tested and found wanting, not merely undertested). On its own home population and stated purpose, the controlled record is null-to-negative:
The mechanism's documented flaw: counting inconsistencies treats evidence items as independent and equally weighted, which they almost never are. Institutional adoption is not outcome evidence. So this skill will not hand you a filled matrix and a "least-inconsistent" verdict, because that artifact is exactly what the trials condemned. It states the caveat and redirects.
When asked to run ACH, follow these steps:
references/TEMPLATE.md.Route to the shipped, better-grounded move the job actually needs:
think-red-team-light.think-evidence-vs-inference-sort.think-what-would-have-to-be-true.Use the template in references/TEMPLATE.md. The deliverable is the honest redirect brief (caveat, real job, evidence-based move), not a disconfirmation matrix.
Before finalizing, verify:
Tier X (tested and found wanting on direct, controlled, repeatedly replicated trials of the actual move). It ships as a contested lens, warn-and-redirect and explicit-request-only, so a by-name request gets an honest answer (the caveat plus the right alternative) rather than a flat refusal or the discredited artifact. The mechanism is genuinely distinct, but distinctness cannot rescue a failed evidence gate. Evidence is the controlled human-subject record above. Full grading: evidence/dossier.md.
See references/EXAMPLE.md for a completed honest redirect brief.
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
npx claudepluginhub mvandermeulen/thinking-framework-skills