The Fool
Stress-test plans, architecture, vendor choices, and business claims with structured devil’s advocate, pre-mortem, and red-team modes before you commit.
Overview
The Fool is a journey-wide agent skill that stress-tests ideas and plans with five structured critical-reasoning modes—usable whenever a solo builder needs to challenge a thesis before committing.
Install
npx skills add https://github.com/jeffallan/claude-skills --skill the-foolWhat is this skill?
- Five structured critical-reasoning modes including devil’s advocate, pre-mortem, and red team
- Core workflow: identify thesis, two-step mode selection, then mode-specific challenge
- Triggers on stress test, poke holes, what could go wrong, and audit evidence
- Output-format report suited for decisions on architecture, vendors, and strategy
- Pairs with architecture-designer, code-reviewer, and feature-forge in related-skills
- 5 structured critical-reasoning modes
- 3-step core workflow: identify, select, challenge
Adoption & trust: 2.3k installs on skills.sh; 9.7k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to commit to a plan, architecture, or strategy but have not adversarially tested assumptions, evidence, or failure modes.
Who is it for?
Indie founders and solo technical leads who want explicit pre-mortems and red-team passes on specs, vendor picks, and launch plans.
Skip if: Hands-on coding, pixel polish, or situations where the decision is already finalized and you only need execution—not when you refuse to restate your thesis for confirmation.
When should I use this skill?
User asks to play the fool, devil’s advocate, stress test, poke holes, pre-mortem, red team, or audit assumptions on a plan or decision.
What do I get? / Deliverables
You receive a structured challenge report that surfaces risks, weak evidence, and blind spots so you can revise scope or design before implementation.
- Structured challenge report for the selected mode
- Documented risks, assumption gaps, and evidence weaknesses
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Challenge whether market evidence actually supports entering a crowded category before you prototype.
Run a pre-mortem on MVP scope to find hidden dependencies and timeline traps.
Red-team a microservices split versus a monolith before you scaffold repos.
Stress-test launch checklist assumptions about auth, secrets, and blast radius.
Audit whether incident runbook steps are evidence-based or ritual copy-paste.
How it compares
Use this adversarial workflow instead of asking the model for agreement on the same plan in casual chat.
Common Questions / FAQ
Who is the-fool for?
Solo builders and small teams who want devil’s advocate, pre-mortem, or red-team rigor on plans, architectures, and business proposals before shipping.
When should I use the-fool?
Use it while validating scope, before major build architecture locks, when red-teaming a design pre-ship, when stress-testing a launch narrative, or when auditing whether evidence supports a growth or ops decision.
Is the-fool safe to install?
It is reasoning and reporting over your context; review the Security Audits panel on this page and avoid pasting live secrets into challenge sessions.
Workflow Chain
Then invoke: architecture designer, code reviewer
SKILL.md
READMESKILL.md - The Fool
# The Fool The court jester who alone could speak truth to the king. Not naive but strategically unbound by convention, hierarchy, or politeness. Applies structured critical reasoning across 5 modes to stress-test any idea, plan, or decision. ## When to Use This Skill - Stress-testing a plan, architecture, or strategy before committing - Challenging technology, vendor, or approach choices - Evaluating business proposals, value propositions, or strategies - Red-teaming a design before implementation - Auditing whether evidence actually supports a conclusion - Finding blind spots and unstated assumptions ## Core Workflow 1. **Identify** — Extract the user's position from conversation context. Restate it as a steelmanned thesis for confirmation. 2. **Select** — Use `AskUserQuestion` with two-step mode selection (see below). 3. **Challenge** — Apply the selected mode's method. Load the corresponding reference file for deep guidance. 4. **Engage** — Present the 3-5 strongest challenges. Ask the user to respond before proceeding. 5. **Synthesize** — Integrate insights into a strengthened position. Offer a second pass with a different mode. ## Mode Selection Use `AskUserQuestion` to let the user choose how to challenge their idea. **Step 1 — Pick a category** (4 options): | Option | Description | |--------|-------------| | Question assumptions | Probe what's being taken for granted | | Build counter-arguments | Argue the strongest opposing position | | Find weaknesses | Anticipate how this fails or gets exploited | | You choose | Auto-recommend based on context | **Step 2 — Refine mode** (only when the category maps to 2 modes): - "Question assumptions" → Ask: "Expose my assumptions" (Socratic) vs "Test the evidence" (Falsification) - "Find weaknesses" → Ask: "Find failure modes" (Pre-mortem) vs "Attack this" (Red team) - "Build counter-arguments" → Skip step 2, proceed with Dialectic synthesis - "You choose" → Skip step 2, load `references/mode-selection-guide.md` and auto-recommend ## 5 Reasoning Modes | Mode | Method | Output | |------|--------|--------| | Expose My Assumptions | Socratic questioning | Probing questions grouped by theme | | Argue the Other Side | Hegelian dialectic + steel manning | Counter-argument and synthesis proposal | | Find the Failure Modes | Pre-mortem + second-order thinking | Ranked failure narratives with mitigations | | Attack This | Red teaming | Adversary profile, attack vectors, defenses | | Test the Evidence | Falsificationism + evidence weighting | Claims audited with falsification criteria | ## Reference Guide | Topic | Reference | Load When | |-------|-----------|-----------| | Socratic questioning | `references/socratic-questioning.md` | "Expose my assumptions" selected | | Dialectic and synthesis | `references/dialectic-synthesis.md` | "Argue the other side" selected | | Pre-mortem analysis | `references/pre-mortem-analysis.md` | "Find the failure modes" selected | | Red team adversarial | `references/red-team-adversarial.md` | "Attack this" selected | | Evidence audit | `references/evidence-audit.md` | "Test the evidence" selected | | Mode selection guide | `references/mode-selection-guide.md` | "You choose" selected or auto-recommend needed | ## Constraints ### MUST DO - Steelman the thesis before challenging it (restate in strongest form) - Use `AskUserQuestion` for mode selection