the-fool

Challenge ideas and plans through five structured critical reasoning modes.

Updated Jan 11, 2017
One-click install
npx skills add https://github.com/kaustubhhiware/dotfiles --skill the-fool-kaustubhhiware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-fool
Source: https://github.com/kaustubhhiware/dotfiles/tree/main/claude/skills/the-fool
Command: npx skills add https://github.com/kaustubhhiware/dotfiles --skill the-fool-kaustubhhiware

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you rigorously stress-test ideas, plans, and decisions by playing devil's advocate, uncovering hidden assumptions, and identifying potential failure points before they occur.

Core Features & Use Cases

  • Structured Critical Reasoning: Applies 5 distinct modes (Socratic, Dialectic, Pre-mortem, Red Team, Evidence Audit) to challenge any proposition.
  • Assumption Probing: Uncovers unstated beliefs and tests the evidence supporting claims.
  • Use Case: Before launching a new product feature, use "The Fool" to run a pre-mortem analysis, identifying potential failure scenarios and developing mitigation strategies.

Quick Start

Use the the-fool skill to challenge my proposal for a new microservices architecture.

Frequently Asked Questions about the-fool

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

FAQPage Schema
What is pre-mortem analysis and when should I use it for decision making?

Pre-mortem analysis is a critical reasoning technique that identifies potential failure scenarios before a decision is finalized. Use it before launching plans or products to uncover hidden assumptions and develop mitigation strategies proactively.

How do I run a red team challenge against a project proposal?

To run a red team challenge, apply structured adversarial reasoning to stress-test the proposition. This involves questioning assumptions, building counter-arguments, and auditing evidence to uncover blind spots through interactive dialogue.

Can I use devil's advocate reasoning to test assumptions in a microservices architecture plan?

Yes, you can use devil's advocate reasoning to test assumptions in a microservices architecture plan. It probes unstated beliefs and audits the evidence supporting claims to identify potential failure points.

What's the best way to uncover hidden assumptions in a product feature plan?

The best way to uncover hidden assumptions is through Socratic questioning and evidence auditing. These critical reasoning modes stress-test propositions interactively, identifying unstated beliefs and blind spots in the plan.

Does assumption testing work for finding failure modes before launching a new feature?

Yes, assumption testing works for finding failure modes before launching a new feature. By applying dialectic reasoning and pre-mortem analysis, it stress-tests decisions to identify potential failure scenarios and blind spots.