agentleFS
babypochi06babypochi06/cc-thinking-skills/skills/thinking-model-router/SKILL.md

thinking-model-router

Skill2 starsChanged 9 months agoMITView on GitHub

Route to the right mental model based on your domain and problem type. The single entry point for all thinking skills.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Core Principle: Don't memorize models—memorize how to find the right one.

    line 12
  2. Distinctive:

    Default for debugging: Start with 5 Whys Plus, escalate to Systems Thinking if it spans components.

    line 58
  3. Distinctive:

    Default for architecture: Start with Reversibility (is this Type 1 or Type 2?), then Systems Thinking for interconnections.

    line 76
  4. Distinctive:

    Default for product: Start with Jobs to be Done (what job is the user hiring this for?).

    line 95
  5. Distinctive:

    Default for strategy: Start with Cynefin (what domain is this problem in?), then match approach.

    line 114
  6. Distinctive:

    Default for personal: Start with Regret Minimization (what will 80-year-old you think?).

    line 132
  7. Distinctive:

    Default for abstract: Start with Steel-manning (argue the strongest opposing view first).

    line 151
  8. Distinctive:

    Default for risk: Start with Pre-mortem (assume failure, explain why).

    line 169
  9. Distinctive:

    Default for innovation: Start with First Principles (strip to fundamentals, rebuild).

    line 187
  10. Distinctive:

    Use Model Combination when:

    line 311

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Model Router

Overview

This is the master routing skill for all mental models. Instead of knowing 38 frameworks, start here. Identify your domain and problem type, and this skill points you to the right model(s). Think of it as the "which tool do I use?" guide.

Core Principle: Don't memorize models—memorize how to find the right one. Domain + Problem Type → Model.

Quick Router

Step 1: What's Your Domain?

DomainYou're working on...
Coding/DebuggingBugs, errors, performance issues, root cause
ArchitectureSystem design, technical decisions, scalability
ProductFeatures, user needs, prioritization, roadmap
Business StrategyCompetition, growth, market, organization
Personal DecisionsCareer, life choices, major commitments
Abstract/AnalyticalArguments, ideas, theories, pure reasoning
Risk/SafetyWhat could go wrong, preparation, resilience
InnovationNew ideas, breakthroughs, creative solutions

Step 2: What's Your Problem Type?

TypeYou need to...
DiagnoseFind root cause, understand why
DecideChoose between options
UnderstandGrasp how something works
CreateGenerate new solutions
EvaluateJudge quality or validity
PredictForecast outcomes
OptimizeImprove performance

Domain → Model Maps

🖥️ Coding & Debugging

PROBLEM                          → MODEL(S)
─────────────────────────────────────────────────────
Bug with unknown cause           → Scientific Method, 5 Whys Plus
Performance degradation          → Theory of Constraints, Systems Thinking
Spans multiple services          → Systems Thinking, Feedback Loops
Incident postmortem              → 5 Whys Plus, Systems Thinking
Flaky/intermittent behavior      → Scientific Method (hypothesis testing)
"It works on my machine"         → Map-Territory (model vs reality gap)

Default for debugging: Start with 5 Whys Plus, escalate to Systems Thinking if it spans components.


🏗️ Architecture & Technical Decisions

PROBLEM                          → MODEL(S)
─────────────────────────────────────────────────────
Technology choice                → Lindy Effect, Reversibility
Build vs buy                     → Opportunity Cost, First Principles
Scalability design               → Systems Thinking, Leverage Points
Microservices vs monolith        → Cynefin, Reversibility
Database selection               → Lindy Effect, Theory of Constraints
API design tradeoffs             → TRIZ (resolve contradictions)
Should we rewrite?               → Second-Order, Opportunity Cost

Default for architecture: Start with Reversibility (is this Type 1 or Type 2?), then Systems Thinking for interconnections.


📦 Product & Feature Development

PROBLEM                          → MODEL(S)
─────────────────────────────────────────────────────
What should we build?            → Jobs to be Done
Feature prioritization           → Opportunity Cost, Theory of Constraints
Why aren't users engaging?       → Jobs to be Done, 5 Whys Plus
New product exploration          → Effectuation, First Principles
Should we pivot?                 → Regret Minimization, Reversibility
Product-market fit               → Jobs to be Done, Scientific Method
Roadmap planning                 → Theory of Constraints, Opportunity Cost
A/B test design                  → Scientific Method, Bayesian

Default for product: Start with Jobs to be Done (what job is the user hiring this for?).


📈 Business Strategy

PROBLEM                          → MODEL(S)
─────────────────────────────────────────────────────
Competitive analysis             → Red Team, Second-Order
Market entry                     → Cynefin, Effectuation
Growth strategy                  → Feedback Loops, Leverage Points
Organizational dysfunction       → Archetypes, Systems Thinking
Resource allocation              → Theory of Constraints, Opportunity Cost
Startup strategy                 → Effectuation, Margin of Safety
M&A evaluation                   → Pre-mortem, Steel-manning
Pricing decisions                → First Principles, Fermi Estimation

Default for strategy: Start with Cynefin (what domain is this problem in?), then match approach.


🧑 Personal & Career Decisions

PROBLEM                          → MODEL(S)
─────────────────────────────────────────────────────
Should I take this job?          → Regret Minimization, Reversibility
Career direction                 → Circle of Competence, Regret Minimization
Major life decision              → Regret Minimization, Pre-mortem
Learning what to learn           → Circle of Competence, Lindy Effect
Negotiation prep                 → Steel-manning, Red Team
Should I start a company?        → Effectuation, Margin of Safety, Pre-mortem
Time allocation                  → Opportunity Cost, Theory of Constraints

Default for personal: Start with Regret Minimization (what will 80-year-old you think?).


🧠 Abstract & Analytical Thinking

PROBLEM                          → MODEL(S)
─────────────────────────────────────────────────────
Evaluating an argument           → Steel-manning, Bayesian
Challenging assumptions          → First Principles, Socratic
Estimating unknowns              → Fermi Estimation, Probabilistic
Updating beliefs                 → Bayesian, Probabilistic
Exploring edge cases             → Thought Experiment, Inversion
Finding logical flaws            → Inversion, Steel-manning
Complex causation                → Systems Thinking, Feedback Loops
Philosophical questions          → Thought Experiment, First Principles

Default for abstract: Start with Steel-manning (argue the strongest opposing view first).


⚠️ Risk & Safety

PROBLEM                          → MODEL(S)
─────────────────────────────────────────────────────
What could go wrong?             → Pre-mortem, Red Team
Security review                  → Red Team, Inversion
Disaster preparation             → Pre-mortem, Margin of Safety
Avoiding catastrophic failure    → Margin of Safety, Via Negativa
Stress-testing plans             → Red Team, Pre-mortem
Probability of failure           → Probabilistic, Bayesian
Building resilience              → Via Negativa, Margin of Safety

Default for risk: Start with Pre-mortem (assume failure, explain why).


💡 Innovation & Creativity

PROBLEM                          → MODEL(S)
─────────────────────────────────────────────────────
Breakthrough needed              → First Principles, TRIZ
Stuck on contradictions          → TRIZ
Limited resources                → Effectuation, Via Negativa
Simplification                   → Via Negativa, Occam's Razor
Challenging "impossible"         → First Principles, TRIZ
New market creation              → Effectuation, Jobs to be Done
Removing complexity              → Via Negativa, Occam's Razor

Default for innovation: Start with First Principles (strip to fundamentals, rebuild).


Quick Reference Card

┌─────────────────────────────────────────────────────────────────┐
│                    MENTAL MODEL QUICK ROUTER                     │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  "Why is this broken?"        → 5 Whys Plus, Scientific Method  │
│  "How does this system work?" → Systems Thinking, Feedback Loops│
│  "What should we build?"      → Jobs to be Done                 │
│  "Should I do this?"          → Reversibility, Regret Min       │
│  "What could go wrong?"       → Pre-mortem, Red Team            │
│  "How do I innovate?"         → First Principles, TRIZ          │
│  "What's the probability?"    → Bayesian, Probabilistic         │
│  "Where's the bottleneck?"    → Theory of Constraints           │
│  "What am I giving up?"       → Opportunity Cost                │
│  "Is this argument valid?"    → Steel-manning                   │
│  "Will this technology last?" → Lindy Effect                    │
│  "How complex is this?"       → Cynefin                         │
│  "What to remove?"            → Via Negativa                    │
│  "Is this safe enough?"       → Margin of Safety                │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Decision Flow

START HERE
    │
    ▼
┌─────────────────────┐
│ What's your domain? │
└──────────┬──────────┘
           │
     ┌─────┴─────┬──────────┬──────────┬──────────┐
     ▼           ▼          ▼          ▼          ▼
  Coding    Architecture  Product   Strategy   Personal
     │           │          │          │          │
     ▼           ▼          ▼          ▼          ▼
┌─────────────────────┐
│ What problem type?  │
│ Diagnose/Decide/    │
│ Understand/Create/  │
│ Evaluate/Predict    │
└──────────┬──────────┘
           │
           ▼
┌─────────────────────┐
│ Look up in domain   │
│ table above         │
└──────────┬──────────┘
           │
           ▼
┌─────────────────────┐
│ Single model enough?│
└──────────┬──────────┘
           │
    ┌──────┴──────┐
    ▼             ▼
   YES           NO
    │             │
    ▼             ▼
 Apply it    Use Model Combination
             (Sequential/Parallel/Nested)

Model Inventory by Category

Diagnostic Models (Find root cause)

  • 5 Whys Plus - Iterative "why" with bias guards
  • Scientific Method - Hypothesis → Test → Learn
  • Kepner-Tregoe - Systematic problem/decision analysis

Decision Models (Choose wisely)

  • Reversibility - Type 1 vs Type 2 decisions
  • Regret Minimization - What will future-you think?
  • Opportunity Cost - What are you giving up?
  • Bayesian - Update beliefs with evidence
  • Probabilistic - Calibrated probability estimates

Systems Models (Understand interconnections)

  • Systems Thinking - Feedback, emergence, non-linearity
  • Feedback Loops - Reinforcing and balancing loops
  • Theory of Constraints - Find and exploit the bottleneck
  • Leverage Points - Where small changes have big effects
  • Archetypes - Recurring system patterns

Risk Models (Prepare for failure)

  • Pre-mortem - Assume failure, explain why
  • Red Team - Attack your own plan
  • Margin of Safety - Build in buffers
  • Inversion - Identify paths to failure, avoid them

Innovation Models (Create breakthroughs)

  • First Principles - Strip to fundamentals, rebuild
  • TRIZ - Resolve technical contradictions
  • Effectuation - Start with means, not goals
  • Via Negativa - Improve by removing

Evaluation Models (Judge quality)

  • Steel-manning - Argue strongest opposing view
  • Lindy Effect - Older = likely to last longer
  • Circle of Competence - Know your expertise boundaries
  • Occam's Razor - Prefer simpler explanations

Context Models (Match approach to situation)

  • Cynefin - Clear/Complicated/Complex/Chaotic domains
  • Model Selection - Choose the right model
  • Model Combination - Use multiple models together

Product Models (Build the right thing)

  • Jobs to be Done - What job is user hiring this for?
  • Thought Experiment - Structured imagination

Estimation Models (Size unknowns)

  • Fermi Estimation - Order-of-magnitude calculations

When to Combine Models

Use Model Combination when:

SituationCombination PatternExample
High-stakes decisionSequentialReversibility → Pre-mortem → Opportunity Cost
System diagnosisNestedCynefin (macro) → ToC (meso) → OODA (micro)
Validating strategyParallelRed Team + Steel-manning + Second-Order
Innovation under constraintsSequentialFirst Principles → TRIZ → Effectuation
Career decisionTemporal5 Whys (past) → Circle of Competence (present) → Regret Min (future)

Template

# Model Router Analysis

## Context
Domain: [Coding/Architecture/Product/Strategy/Personal/Abstract/Risk/Innovation]
Problem: [Brief description]
Problem Type: [Diagnose/Decide/Understand/Create/Evaluate/Predict/Optimize]

## Routed Models
Primary: [Main model to use]
Secondary: [If needed]
Combination pattern: [Sequential/Parallel/Nested/None]

## Application
[Apply the selected model(s) here]

## Verification
- [ ] Domain correctly identified
- [ ] Problem type matches
- [ ] Model fits the situation
- [ ] Considered if combination needed

Key Questions

  • "What domain am I operating in?"
  • "What type of problem is this—diagnose, decide, understand, create, or evaluate?"
  • "What's the default model for this domain + type?"
  • "Does one model cover it, or do I need to combine?"
  • "Am I using a model because it fits, or because it's familiar?"

Remember: You don't need to know all 38 models. You need to know how to find the right one. Start with domain, identify problem type, look it up, apply. That's it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.