the-fool

Restate a user's plan as a steelmanned thesis and run mode-specific adversarial reasoning.

1|Updated Mar 6, 2026

Search Tags:#decision making #strategy #assumption testing #risk analysis #pre-mortem #red teaming #evidence audit

Ready to run

npx skills add https://github.com/barateza/dubweave --skill the-fool-barateza

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: the-fool
Source: https://github.com/barateza/dubweave/tree/main/.agent/skills/the-fool
Command: npx skills add https://github.com/barateza/dubweave --skill the-fool-barateza

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you avoid committing to weak plans by systematically challenging your assumptions, evidence, and blind spots before you act.

Core Features & Use Cases

Steelman-first critique: Restates your position as the strongest version and validates it before attacking.
Mode-based adversarial reasoning: Runs targeted challenge styles such as assumption probing, counter-argument construction, failure-mode pre-mortems, red teaming, and evidence audits.
Cognitive bias scan woven into critiques: Flags common reasoning patterns that can distort judgment and reframes challenges accordingly.
Engagement-first workflow: Presents 3–5 high-quality challenges and requires your responses before synthesis.

Quick Start

Use the the-fool skill when you want a rigorous pre-commit critique of an idea, proposal, or decision you are considering right now.

Frequently Asked Questions about the-fool

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

FAQPage Schema

What is structured skepticism and how does it stress-test a business strategy?▼

Structured skepticism stress-tests a business strategy by restating your plan as a steelmanned thesis, then running adversarial reasoning modes like red teaming and pre-mortem analysis to expose blind spots. It validates the strongest version of your idea before attacking it.

How do I run a pre-mortem analysis on a project proposal?▼

To run a pre-mortem analysis, present your project proposal and select the pre-mortem challenge mode. The system generates 3–5 targeted failure-mode critiques, requires your responses to each, and synthesizes a post-response evaluation with confidence levels and next-step experiments.

Can I use red teaming for assumption testing in software architecture decisions?▼

Yes, red teaming applies directly to assumption testing in software architecture decisions. The system probes underlying assumptions, constructs counter-arguments, and scans for cognitive biases that distort judgment across technology and decision-making contexts.

What is the best way to audit evidence before committing to a decision?▼

The best way to audit evidence is using the evidence auditing mode, which challenges the validity of supporting data within your proposal. It flags common reasoning patterns that distort judgment and reframes challenges to ensure grounded critiques before you commit.

When should I not use adversarial reasoning for risk analysis?▼

Adversarial reasoning for risk analysis is not suited for decisions requiring immediate, reflexive action without time for a structured workflow. The process demands user-confirmed thesis restatement and engagement with 3–5 high-quality challenges before synthesis.

Does the fool skill require any specific input format for decision making?▼

No specific input format is required for decision making. You simply provide your plan, decision, or proposal as a natural language description, which the system then restates as a validated, steelmanned thesis before initiating mode-specific adversarial critiques.