the-fool

Challenges ideas and decisions using five structured critical reasoning modes.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ArMaTeC/Redball --skill the-fool-armatec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-fool
Source: https://github.com/ArMaTeC/Redball/tree/main/.devin/skills/the-fool
Command: npx skills add https://github.com/ArMaTeC/Redball --skill the-fool-armatec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Plans, architectures, and decisions often ship with unexamined assumptions, weak evidence, or hidden failure modes. This Skill stress-tests any idea before commitment by applying structured critical reasoning instead of vague skepticism. ## Core Features & Use Cases - Five Reasoning Modes: Socratic assumption exposure, dialectic counter-argument, pre-mortem failure analysis, red team adversarial attack, and evidence audit with falsification criteria. - Guided Mode Selection: Uses structured questions to help users pick the right challenge method, with an auto-recommendation guide based on context signals. - Synthesis-Driven Output: Every challenge ends with a strengthened position, mitigations, or defenses rather than a pile of objections. - Use Case: Before committing to a microservices migration, run a pre-mortem to generate ranked failure narratives with early warning signs and concrete mitigations. ## Quick Start Ask the assistant to play devil's advocate on your plan and stress-test it before you commit.

Frequently Asked Questions about the-fool

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

FAQPage Schema
How do I stress-test a plan before committing to it?

Use the pre-mortem mode, which imagines the plan has already failed and generates specific failure narratives ranked by likelihood and impact. Each narrative includes consequence chains, early warning signs, and concrete mitigations.

What is the difference between red teaming and pre-mortem analysis?

Pre-mortem analysis finds internal failure modes by imagining the plan already failed, while red teaming adopts an external adversary's perspective to find exploitable weaknesses. Pre-mortem suits reliability concerns; red teaming suits security and competitive threats.

How do I check if evidence actually supports a conclusion?

Use the evidence audit mode, which extracts claims, designs falsification criteria for each, grades evidence quality from A to F, checks for cognitive biases, and surfaces competing explanations for the same data.

Can this skill challenge business decisions or only technical ones?

It handles both. The mode selection guide maps decision types like vendor selection, business strategy, hiring, and architecture to appropriate reasoning modes, with domain-specific question banks for technical, business, and strategic decisions.

When should I not use devil's advocate reasoning?

Avoid it when the question is narrow and already resolved, or when the user needs execution rather than evaluation. The skill also prohibits nihilistic criticism and always requires synthesis, so it is unsuitable if you only want validation.