Audit the decision before it ships. Use for "are we sure about this?", high-stakes choices made on fast intuition, plans with no failure scenario, estimates that are suspiciously optimistic, metrics being gamed (Goodhart), unfalsifiable claims, negotiation prep, or strategies that break in extreme conditions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zetetic-team-subagents:decision-bias-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Problem shape:** a decision, plan, or evaluation is about to be committed and
Problem shape: a decision, plan, or evaluation is about to be committed and nobody has run the adversarial pass: which bias produced it, what would refute it, how it behaves in the tails, and whether the metric still measures what it was meant to.
| Agent | Use when |
|---|---|
| kahneman | fast intuition on a high-stakes call; no pre-mortem; estimate needs a reference class; an easier question was answered instead of the hard one |
| taleb | exposure to volatility unclassified (fragile/robust/antifragile); improvement always by addition; decision-makers carry no downside |
| popper | claim has no observation that could refute it; only easy confirmations offered as evidence; plan too big to test piecemeal |
| simon | optimizing where satisficing is rational; the search space needs decomposing before choosing |
| boyd | adversarial setting — the other side adapts; tempo and orientation matter more than the single best move |
| zhuangzi | the metric has become the target (Goodhart); the evaluation framework itself needs auditing |
| ibnalhaytham | an authority's claim taken on trust — systematic doubt with controlled isolation of variables |
| rogerfisher | multi-stakeholder deadlock — separate interests from positions, find the BATNA and the zone of agreement |
tools/genius-invoker.sh route "<problem>" and take the top ranked match.tools/genius-invoker.sh invoke <agent> "<problem>", then read
agents/genius/<agent>.md in full.<workflow> step by step and answer in its
<output-format>. The output names the specific bias/failure with its
evidence — not a generic "consider other perspectives".tools/genius-invoker.sh compose kahneman popper -- "<problem>".npx claudepluginhub cdeust/cortex --plugin zetetic-team-subagentsGuides 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.