descartes-methodical-doubt

Systematically doubt beliefs through sensory, reasoning, and systemic questioning.

6|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/kouko/monkey-skills --skill descartes-methodical-doubt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: descartes-methodical-doubt
Source: https://github.com/kouko/monkey-skills/tree/main/philosophers-toolkit/skills/descartes-methodical-doubt
Command: npx skills add https://github.com/kouko/monkey-skills --skill descartes-methodical-doubt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams and individuals rigorously test beliefs, assumptions, and evidence by applying systematic skepticism to reveal what truly survives doubt and what must be discarded or re-validated before acting.

Core Features & Use Cases

  • Structured four-layer process: guide users to state a belief, apply sensory/reasoning/systemic doubt, identify what survives, and rebuild from that foundation.
  • Interactive, stop-after-phase workflow: enforces one-step-at-a-time questioning and waits for user input between layers to avoid premature conclusions.
  • Use cases: auditing security assumptions, validating data-driven decisions, pre-mortem stress tests, and challenging entrenched organizational beliefs.

Quick Start

Use the descartes-methodical-doubt skill to examine the belief that our API is secure because we use JWT and HTTPS.

Frequently Asked Questions about descartes-methodical-doubt

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

FAQPage Schema
How do I test assumptions for a technical decision using methodical doubt?

Pre-mortem stress tests benefit from methodical doubt by systematically challenging entrenched organizational beliefs and security assumptions. The stepwise questioning process reveals what truly survives doubt and what must be re-validated before acting.

What is the best way to audit security assumptions before deployment?

Auditing security assumptions is best achieved by applying systematic skepticism through a four-layer process. This interactive workflow enforces step-by-step questioning to validate data-driven claims and identify indubitable foundations for your security decisions.

How does methodical doubt validate data-driven claims?

Methodical doubt validates data-driven claims by guiding users to state a belief, apply sensory and reasoning doubt, identify what survives, and rebuild from that foundation. This structured workflow prevents premature conclusions through stop-after-phase behavior.

Can I use methodical doubt for pre-mortem stress tests on organizational beliefs?

Pre-mortem stress tests benefit from methodical doubt by systematically challenging entrenched organizational beliefs and security assumptions. The stepwise questioning process reveals what truly survives doubt and what must be re-validated before acting.

Does the methodical doubt process require external dependencies or tools?

The methodical doubt process requires no external dependencies or tools. It is an interactive, stepwise questioning workflow that systematically applies sensory, reasoning, and systemic doubt layers to rebuild decisions from indubitable foundations.