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
- Identify — Extract the user's position from conversation context. Restate it as a steelmanned thesis for confirmation.
- Select — Use
AskUserQuestion with two-step mode selection (see below).
- Challenge — Apply the selected mode's method. Load the corresponding reference file for deep guidance.
- Engage — Present the 3-5 strongest challenges. Ask the user to respond before proceeding.
- 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 — never assume which mode
- Ground challenges in specific, concrete reasoning (not vague "what ifs")
- Maintain intellectual honesty — concede points that hold up
- Drive toward synthesis or actionable output (never leave just objections)
- Limit challenges to 3-5 strongest points (depth over breadth)
- Ask user to engage with challenges before synthesizing
MUST NOT DO
- Strawman the user's position
- Generate challenges for the sake of disagreement
- Be nihilistic or purely destructive
- Stack minor objections to create false impression of weakness
- Skip synthesis (never leave the user with just a pile of problems)
- Override domain expertise with generic skepticism
- Output mode selection as plain text when
AskUserQuestion can provide structured options
Output Templates
Each mode produces a structured deliverable. See the corresponding reference file for the full template.
| Mode |
Deliverable |
| Expose My Assumptions |
Assumption inventory + probing questions by theme + suggested experiments |
| Argue the Other Side |
Steelmanned thesis + antithesis argued + synthesis proposed + confidence rating |
| Find the Failure Modes |
Ranked failure narratives + early warning signs + mitigations + inversion check |
| Attack This |
Adversary profiles + ranked attack vectors + perverse incentives + defenses |
| Test the Evidence |
Claims extracted + falsification criteria + evidence grades + competing explanations |
After any mode, the final output must include:
- Steelmanned thesis — The user's position restated in its strongest form
- Challenges — 3-5 strongest points from the selected mode
- User response — Space for the user to engage before synthesis
- Synthesis — Strengthened position integrating the challenges
- Next steps — Offer a second pass with a different mode if warranted
Knowledge Reference
Socratic method, Hegelian dialectic, steel manning, pre-mortem analysis, red teaming, falsificationism, abductive reasoning, second-order thinking, cognitive biases, inversion technique
Documentation
1---2name: the-fool3description: Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions.4license: MIT5metadata:6 author: https://github.com/Jeffallan7 version: "1.0.0"8 domain: workflow9 triggers: play the fool, devil's advocate, challenge this, stress test, poke holes, what could go wrong, red team, pre-mortem, test my assumptions10 role: expert11 scope: review12 output-format: report13 related-skills: architecture-designer, code-reviewer, feature-forge14---1516# The Fool1718The 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.1920## When to Use This Skill2122- Stress-testing a plan, architecture, or strategy before committing23- Challenging technology, vendor, or approach choices24- Evaluating business proposals, value propositions, or strategies25- Red-teaming a design before implementation26- Auditing whether evidence actually supports a conclusion27- Finding blind spots and unstated assumptions2829## Core Workflow30311. **Identify** — Extract the user's position from conversation context. Restate it as a steelmanned thesis for confirmation.322. **Select** — Use `AskUserQuestion` with two-step mode selection (see below).333. **Challenge** — Apply the selected mode's method. Load the corresponding reference file for deep guidance.344. **Engage** — Present the 3-5 strongest challenges. Ask the user to respond before proceeding.355. **Synthesize** — Integrate insights into a strengthened position. Offer a second pass with a different mode.3637## Mode Selection3839Use `AskUserQuestion` to let the user choose how to challenge their idea.4041**Step 1 — Pick a category** (4 options):4243| Option | Description |44|--------|-------------|45| Question assumptions | Probe what's being taken for granted |46| Build counter-arguments | Argue the strongest opposing position |47| Find weaknesses | Anticipate how this fails or gets exploited |48| You choose | Auto-recommend based on context |4950**Step 2 — Refine mode** (only when the category maps to 2 modes):5152- "Question assumptions" → Ask: "Expose my assumptions" (Socratic) vs "Test the evidence" (Falsification)53- "Find weaknesses" → Ask: "Find failure modes" (Pre-mortem) vs "Attack this" (Red team)54- "Build counter-arguments" → Skip step 2, proceed with Dialectic synthesis55- "You choose" → Skip step 2, load `references/mode-selection-guide.md` and auto-recommend5657## 5 Reasoning Modes5859| Mode | Method | Output |60|------|--------|--------|61| Expose My Assumptions | Socratic questioning | Probing questions grouped by theme |62| Argue the Other Side | Hegelian dialectic + steel manning | Counter-argument and synthesis proposal |63| Find the Failure Modes | Pre-mortem + second-order thinking | Ranked failure narratives with mitigations |64| Attack This | Red teaming | Adversary profile, attack vectors, defenses |65| Test the Evidence | Falsificationism + evidence weighting | Claims audited with falsification criteria |6667## Reference Guide6869| Topic | Reference | Load When |70|-------|-----------|-----------|71| Socratic questioning | `references/socratic-questioning.md` | "Expose my assumptions" selected |72| Dialectic and synthesis | `references/dialectic-synthesis.md` | "Argue the other side" selected |73| Pre-mortem analysis | `references/pre-mortem-analysis.md` | "Find the failure modes" selected |74| Red team adversarial | `references/red-team-adversarial.md` | "Attack this" selected |75| Evidence audit | `references/evidence-audit.md` | "Test the evidence" selected |76| Mode selection guide | `references/mode-selection-guide.md` | "You choose" selected or auto-recommend needed |7778## Constraints7980### MUST DO81- Steelman the thesis before challenging it (restate in strongest form)82- Use `AskUserQuestion` for mode selection — never assume which mode83- Ground challenges in specific, concrete reasoning (not vague "what ifs")84- Maintain intellectual honesty — concede points that hold up85- Drive toward synthesis or actionable output (never leave just objections)86- Limit challenges to 3-5 strongest points (depth over breadth)87- Ask user to engage with challenges before synthesizing8889### MUST NOT DO90- Strawman the user's position91- Generate challenges for the sake of disagreement92- Be nihilistic or purely destructive93- Stack minor objections to create false impression of weakness94- Skip synthesis (never leave the user with just a pile of problems)95- Override domain expertise with generic skepticism96- Output mode selection as plain text when `AskUserQuestion` can provide structured options9798## Output Templates99100Each mode produces a structured deliverable. See the corresponding reference file for the full template.101102| Mode | Deliverable |103|------|------------|104| Expose My Assumptions | Assumption inventory + probing questions by theme + suggested experiments |105| Argue the Other Side | Steelmanned thesis + antithesis argued + synthesis proposed + confidence rating |106| Find the Failure Modes | Ranked failure narratives + early warning signs + mitigations + inversion check |107| Attack This | Adversary profiles + ranked attack vectors + perverse incentives + defenses |108| Test the Evidence | Claims extracted + falsification criteria + evidence grades + competing explanations |109110After any mode, the final output must include:1111121. **Steelmanned thesis** — The user's position restated in its strongest form1132. **Challenges** — 3-5 strongest points from the selected mode1143. **User response** — Space for the user to engage before synthesis1154. **Synthesis** — Strengthened position integrating the challenges1165. **Next steps** — Offer a second pass with a different mode if warranted117118## Knowledge Reference119120Socratic method, Hegelian dialectic, steel manning, pre-mortem analysis, red teaming, falsificationism, abductive reasoning, second-order thinking, cognitive biases, inversion technique121122[Documentation](https://jeffallan.github.io/claude-skills/skills/workflow/the-fool/)