thinking-occams-razor

Guide hypothesis generation, assumption counting, and testing to select the simplest explanation.

Updated Jan 14, 2022
One-click install
npx skills add https://github.com/alexmarucci/dotfiles --skill thinking-occams-razor-alexmarucci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thinking-occams-razor
Source: https://github.com/alexmarucci/dotfiles/tree/main/claude/agents/the-thinker/skills/thinking-occams-razor
Command: npx skills add https://github.com/alexmarucci/dotfiles --skill thinking-occams-razor-alexmarucci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in applying Occam's Razor to simplify and validate explanations for complex problems, making it easier to identify the most likely cause.

Core Features & Use Cases

  • Hypothesis Generation: Encourage the user to list all possible explanations for a given situation.
  • Assumption Counting: Guide the user through counting the number of assumptions each hypothesis requires.
  • Explanatory Power Verification: Assist the user in determining which hypothesis is the simplest and has the same explanatory power.
  • Testing Hypotheses: Advise the user on how to test simpler hypotheses first.
  • Complexity Assessment: Provide a framework for evaluating the complexity of solutions.

Quick Start

To use Occam's Razor, list your hypotheses about the system failure and follow the structured process to select the simplest explanation.

Frequently Asked Questions about thinking-occams-razor

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

FAQPage Schema
How do I apply Occam's Razor to debugging and system analysis?

Occam's Razor is a problem-solving principle stating that the simplest explanation with the fewest assumptions is most likely correct. This Skill structures that process by guiding hypothesis generation, assumption counting, and explanatory power verification for system analysis.

What is the best way to evaluate the complexity of architecture hypotheses?

The best way to evaluate architecture hypotheses is to count the number of assumptions each requires and verify which simplest option provides the same explanatory power, ensuring structured decision-making over unnecessary complexity.

How do I test hypotheses to find the simplest explanation for a problem?

You test hypotheses by listing all possible explanations, counting the assumptions each requires, and then validating the simpler hypotheses first before moving to more complex ones, ensuring efficient problem-solving and decision-making.

Do I need structured thinking skills to use assumption counting for decision-making?

Yes, applying Occam's Razor for decision-making requires structured thinking and analytical skills to accurately generate hypotheses, count underlying assumptions, and assess the complexity of potential solutions during system analysis.

When should I avoid selecting the simplest explanation during system analysis?

You should avoid selecting the simplest explanation when a hypothesis lacks sufficient explanatory power for the observed system failure, requiring you to test more complex hypotheses that account for all variables and edge cases.