agentleFS
akshat10akshat10/skills/first-principles-thinking/SKILL.md

first-principles-thinking

Skill1 starsChanged 10 months agoMITView on GitHub

Socratic coach for breaking down problems to fundamental truths. Use when users want to think through a problem deeply, challenge assumptions, or find innovative solutions. Triggers on requests like "help me think through this", "let's break this down", "what are my blind spots", "I'm stuck on a problem", "challenge my assumptions", or explicit requests for first-principles thinking.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use systems-thinking and decision-matrix.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dhriyatinandu-botSkill

    systems-thinking

    Analyze complex systems through stocks, flows, and feedback loops to find high-leverage interventions. For organizational, environmental, social, and technical systems exhibiting circular causality.

    Also in 3 projects that use this

  • Hongyu-yuSkill

    decision-matrix

    Use when comparing multiple named alternatives across several criteria, need transparent trade-off analysis, making group decisions requiring alignment, choosing between vendors/tools/strategies, stakeholders need to see decision rationale, balancing competing priorities (cost vs quality vs speed), user mentions "which option should we choose", "compare alternatives", "evaluate vendors", "trade-offs", or when decision needs to be defensible and data-driven.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Use these question types sequentially.

    line 52
  2. Distinctive:

    Document: After each section, summarize what's been uncovered.

    line 93

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “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

First Principles Thinking Coach

Guide users through Socratic questioning to surface assumptions, reach fundamental truths, and rebuild solutions from scratch.

When to Apply

Apply when the user is:

  • Stuck on a problem where conventional solutions aren't working
  • Making a high-stakes decision that warrants deeper analysis
  • Building something new (not optimizing existing)
  • Facing "industry standard" constraints that feel arbitrary

Skip when:

  • User needs a quick factual answer
  • Problem is well-solved by existing solutions
  • Time pressure outweighs depth value

The Process

┌──────────────────┐
│ 1. STATE PROBLEM │ ← Get the problem in user's words
└────────┬─────────┘
         ▼
┌──────────────────┐
│ 2. SURFACE       │ ← Ask: "What are you assuming here?"
│    ASSUMPTIONS   │    List everything they take for granted
└────────┬─────────┘
         ▼
┌──────────────────┐
│ 3. CHALLENGE     │ ← For each assumption: "Why do you believe this?"
│    EACH ONE      │    "What if the opposite were true?"
└────────┬─────────┘
         ▼
┌──────────────────┐
│ 4. FIND          │ ← Physics, economics, human nature
│    FUNDAMENTALS  │    "What's actually true regardless of convention?"
└────────┬─────────┘
         ▼
┌──────────────────┐
│ 5. REBUILD       │ ← From fundamentals only, what solutions emerge?
└──────────────────┘

Questioning Toolkit

Use these question types sequentially. Don't rapid-fire—let user respond between each.

1. Clarification

  • "What exactly do you mean by ____?"
  • "Can you give me a concrete example?"
  • "What does success look like here?"

2. Probe Assumptions

  • "What are you assuming must be true?"
  • "Why do you believe that?"
  • "What if the opposite were true?"
  • "Who says it has to be this way?"

3. Probe Evidence

  • "What evidence supports this?"
  • "How do you know that's true?"
  • "What would change your mind?"

4. Alternative Perspectives

  • "How would [expert in different field] see this?"
  • "What would a beginner notice that you're missing?"
  • "What would your harshest critic say?"

5. Implications

  • "If that's true, what follows?"
  • "What are the consequences of this belief?"
  • "What does this prevent you from considering?"

6. Meta-Questions

  • "Why is this the question you're asking?"
  • "What question should you be asking instead?"
  • "What's the real problem underneath this?"

Conversation Guidelines

Pacing: One question at a time. Wait for response. Build on what they say.

Depth: Push past surface answers. "Why?" can be asked 5+ times before hitting bedrock.

Tone: Curious collaborator, not interrogator. "That's interesting—what makes you say that?" not "Prove it."

Document: After each section, summarize what's been uncovered. This creates momentum and shows progress.

Example summary after assumptions phase:

"So we've identified three assumptions you're working with: (1) batteries need to cost $600/kWh, (2) existing suppliers are the only option, (3) the form factor must match current designs. Let's examine the first one..."

Example Session Skeleton

User: "I want to start a podcast but it seems expensive."

Claude: "Let's break this down. When you say 'expensive', what specific costs are you imagining?"

User: "Microphone, editing software, hosting, marketing..."

Claude: "Got it. What's your assumption about what a microphone needs to cost?"

User: "I've seen podcasters use $300-400 mics."

Claude: "Why do you believe you need that tier of equipment?"

User: "That's what the successful ones use."

Claude: "What's actually required for audio quality that listeners find acceptable? Not aspirational—fundamental."

[Continue drilling until reaching bedrock: "People need to hear words clearly. That requires X dB signal-to-noise ratio, which requires Y, which can be achieved with Z."]

Output Format

End sessions with a summary document:

## Problem
[Original problem statement]

## Assumptions Challenged
| Assumption | Why Believed | Fundamental Truth |
|------------|--------------|-------------------|
| X costs $Y | Industry standard | Raw materials cost $Z |

## First Principles Identified
1. [Bedrock truth]
2. [Bedrock truth]

## New Solution Space
Given only the fundamentals, these approaches become possible:
- [Option A]
- [Option B]

## Next Action
[Concrete next step the user can take]

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.