the-fool

Stress-test plans and decisions through Socratic questioning, red teaming, and pre-mortem analysis.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill the-fool-design-system-et
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-fool
Source: https://github.com/Design-System-ET/genexus-dev-opencode/tree/main/skills/the-fool
Command: npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill the-fool-design-system-et

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents costly mistakes and blind spots by providing a structured, objective framework to challenge your plans, assumptions, and decisions before you commit to them.

Core Features & Use Cases

  • Structured Critical Reasoning: Choose from five distinct modes including Socratic questioning, red teaming, and pre-mortem analysis to stress-test any proposal.
  • Objective Auditing: Use the evidence audit mode to verify if your claims are actually supported by data or if they rely on cognitive biases.
  • Use Case: Before launching a new system architecture, invoke this skill to run a pre-mortem analysis, identifying potential failure modes and designing mitigations before a single line of code is written.

Quick Start

Invoke the fool skill to begin a red team analysis of your current project proposal.

Frequently Asked Questions about the-fool

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

FAQPage Schema
How do I run a pre-mortem analysis on a system architecture before committing to code?

To run a pre-mortem analysis, invoke this skill to identify potential failure modes in your system architecture and design mitigations before writing any code. It applies structured critical reasoning to stress-test your proposal.

What is red teaming and when should I use it to stress-test a strategy?

Red teaming is a critical reasoning mode used to challenge assumptions and find blind spots in high-stakes environments. You should use it to stress-test your strategy and ensure intellectual honesty before finalizing a decision.

Can I audit evidence and verify if my project claims are supported by data?

Yes, you can audit evidence using the objective auditing mode to verify if your project claims are actually supported by data or rely on cognitive biases. This validates assumptions and ensures rigorous evidence checks.

What is the best way to identify blind spots in a high-stakes decision making process?

The best way to identify blind spots is applying structured critical reasoning through Socratic questioning. This framework challenges your plans and decisions objectively to expose hidden vulnerabilities in high-stakes environments.

Are there limitations to using structured reasoning for critical thinking in professional workflows?

Structured reasoning requires intellectual honesty to effectively validate assumptions and audit evidence. It is limited if the input lacks concrete data, as objective auditing depends on verifying actual claims rather than abstract concepts.