RCP-000-000-005-FIRST-PRINCIPLES-PROBLEM-SOLVER – First Principles Problem Solver

Takes a stubborn problem and strips it down to bedrock. Instead of asking “how do we fix this?” the AI guides you to ask “what is actually, undeniably true here?” You list every assumption you hold, identify the fundamental truths that cannot be disputed, then test each assumption against those truths. Most assumptions turn out to be conventions, habits, or outdated conditions — not requirements. Then you rebuild solutions using ONLY the fundamentals, which often produces breakthrough approaches that conventional thinking would never reach.

Recipe Name: RCP-000-000-005-FIRST-PRINCIPLES-PROBLEM-SOLVER – First Principles Problem Solver
RCP-000-000-005-FIRST-PRINCIPLES-PROBLEM-SOLVER
Apply first principles thinking to break down any problem
into its most fundamental components, question every
assumption, and rebuild innovative solutions from the
ground up. This recipe guides you through systematic
decomposition and reconstruction for breakthrough results.
Multi-Recipe Combo Stage Single Recipe
Recipe Category Standalone
Recipe Subcategory Critical Thinking, Problem-Solving, Strategy
Recipe Difficulty Easy

Requirements

  • Any AI Chat Platform (platform-agnostic recipe) Any of the following: Claude (Anthropic), ChatGPT (OpenAI), Gemini (Google), Grok (X.ai), Perplexity, Microsoft Copilot

TL;DR

Takes a stubborn problem and strips it down to bedrock.
Instead of asking "how do we fix this?" the AI guides you
to ask "what is actually, undeniably true here?" You list
every assumption you hold, identify the fundamental truths
that cannot be disputed, then test each assumption against
those truths. Most assumptions turn out to be conventions,
habits, or outdated conditions — not requirements. Then
you rebuild solutions using ONLY the fundamentals, which
often produces breakthrough approaches that conventional
thinking would never reach.
HOW IT WORKS:
Nine steps. You define the problem. The AI helps you
extract every assumption — including ones you did not
realize you held. Together you identify irreducible
fundamental truths. Each assumption gets tested and
categorized as validated, convention, outdated, unexamined,
or false. Then you rebuild at least three solutions from
fundamentals only. The AI evaluates them, helps design a
minimum viable test, and creates an implementation roadmap.
WHAT TO EXPECT:
This is the most rigorous recipe in the collection. It
will challenge things you take for granted. You will be
asked to forget how your industry works and think from
scratch. Some of what you "know" will turn out to be
convention, not truth. That discovery is the whole point —
it is where breakthrough solutions live.
BEST RESULTS WHEN YOU:
– Bring a problem that has resisted conventional solutions
– Are willing to question everything, even "obvious" truths
– Have 30-60 minutes for thorough analysis
– Share what you have already tried (failed attempts reveal
assumptions)
– Define what success looks like before starting
TIME: 30-60 minutes for thorough analysis
DIFFICULTY: Advanced — requires deep thinking and
willingness to question fundamentals

How To Start
 

STEP 1: Define Your Problem Clearly
  • State the problem you want to solve. Be specific about:
    – What exactly is the problem?
    – Who does it affect?
    – What have you already tried?
    – Why haven't previous solutions worked?
    – What would success look like?
    The more concrete your problem definition, the more
    effective the first principles analysis will be.
    Examples of well-defined problems:
    – "Customer acquisition cost is $150, but lifetime
    value is only $120, making growth unsustainable"
    – "Our product takes 6 months to ship, but market
    windows only last 3 months"
    – "Employee turnover is 40% annually despite
    above-market compensation"
STEP 2: List Current Assumptions
  • Identify everything you currently believe about this
    problem and how it is typically solved. Include:
    INDUSTRY ASSUMPTIONS:
    What does conventional wisdom say about this?
    How do competitors handle it?
    What are the "accepted" best practices?
    YOUR ASSUMPTIONS:
    What do you believe causes the problem?
    What constraints do you assume exist?
    What solutions have you assumed won't work?
    HISTORICAL ASSUMPTIONS:
    Why do current approaches exist?
    When were they established?
    What conditions existed then vs now?
    Be brutally honest. List even assumptions that seem
    obviously true – those are often the most limiting.
STEP 3: Identify Fundamental Truths
  • Strip the problem down to its irreducible components.
    Ask: "What do we know to be absolutely, undeniably true?"
    PHYSICAL TRUTHS:
    Laws of physics, biology, chemistry that apply
    Geographic or temporal constraints
    Resource limitations that cannot be changed
    HUMAN TRUTHS:
    Core human needs and motivations
    Psychological principles that govern behavior
    Universal patterns in how people act
    MATHEMATICAL TRUTHS:
    Economic fundamentals (supply/demand, margins)
    Statistical realities in your data
    Logical constraints and dependencies
    For each "truth" ask: Can this be further reduced?
    Keep going until you hit bedrock – things that cannot
    be broken down further or disputed.
STEP 4: Challenge Each Assumption
  • Take each assumption from Step 2 and test it against
    the fundamental truths from Step 3.
    For each assumption, ask:
    "Is this assumption NECESSARILY true given
    the fundamental truths I identified?"
    "Does this assumption exist because of
    fundamental constraints, or because of
    convention, habit, or outdated conditions?"
    "If I were starting fresh today with only
    the fundamental truths, would I arrive
    at this same assumption?"
    "What evidence would prove this assumption
    wrong? Does such evidence exist?"
    Categorize each assumption:
    VALIDATED: Directly follows from fundamentals
    CONVENTION: Exists due to industry habit
    OUTDATED: Made sense historically, not now
    UNEXAMINED: Accepted without evidence
    FALSE: Contradicts fundamental truths
STEP 5: Rebuild From Fundamentals
  • Using ONLY the fundamental truths and validated
    assumptions, construct new approaches to the problem.
    IGNORE:
    – How others solve this problem
    – What you have tried before
    – What seems "realistic" or "practical"
    – Industry standards and best practices
    USE ONLY:
    – Fundamental truths you identified
    – Validated assumptions that passed testing
    – Logical reasoning from these foundations
    Generate at least THREE distinct solutions that:
    1. Address the problem's root cause
    2. Build only on validated fundamentals
    3. May seem unconventional or radical
    For each solution, trace its logic back to
    the fundamentals it builds upon.
STEP 6: Evaluate New Approaches
  • Compare your first-principles solutions against
    traditional approaches.
STEP 7: Design Validation Experiments
  • Before full commitment, design small tests for your
    top solution.
STEP 8: Implementation Roadmap
  • For validated solutions, create a phased action plan.
STEP 9: Follow-Up Options
  • After completing the analysis, choose next steps.

How AI Reads This Recipe

The AI guides you through systematic first principles
decomposition. It helps identify assumptions you may not
recognize, challenges you to find irreducible truths,
and assists in rebuilding solutions from fundamentals
only. The AI maintains intellectual rigor throughout,
pushing you to strip away convention and think from
bedrock principles. It will not accept "that's just
how it's done" as justification for any assumption.

When to Use This Recipe

Use this recipe when you:
– Face a persistent problem that resists conventional
solutions
– Suspect hidden assumptions are constraining your
thinking
– Want to find breakthrough approaches, not incremental
improvements
– Are entering a new market and want to avoid inheriting
incumbent assumptions
– Need to justify a radical approach with rigorous logic
Do NOT use this recipe when:
– You need a quick answer (this takes 30-60 minutes)
– The problem is simple and well-understood
– You want to optimize an existing approach (use
SOCRATIC-OPTIMIZER instead)
– You want to question beliefs generally (use
SOCRATIC-PROBLEM-SOLVER instead)

Recipe FAQ

Q: How is this different from SOCRATIC-PROBLEM-SOLVER?
A: Socratic method challenges beliefs through questions
like “Why do you believe that?” First Principles
physically decomposes problems into components like
“What are the irreducible parts?” Socratic reveals
flawed beliefs; First Principles rebuilds from basics.
They complement each other.
Q: How do I know if something is truly fundamental?
A: Keep asking “Can this be reduced further?” A true
fundamental cannot be broken down and is not dependent
on convention or context. Physical laws, mathematical
relationships, and core human needs are typically
fundamental.
Q: What if my rebuilt solution seems impractical?
A: “Impractical” often means “challenges too many
conventions at once.” Identify which conventions are
truly constraining vs existing from habit. Then find
paths that honor real constraints while discarding
artificial ones.
Q: How long does this take?
A: Initial analysis: 30-60 minutes. For complex problems
you may need multiple sessions. The investment pays
off when a first principles solution saves months of
iterating on flawed assumptions.
Q: Can I use this for small problems?
A: It works at any scale, but the effort is similar
regardless of problem size. Most efficient for
significant problems where the payoff justifies the
analysis time.

Actual Recipe Code

(Copy This Plaintext Code To Use)
# ===========================================================
# MERGED RECIPE-ID: RCP-000-000-001-SOCRATIC-PROBLEM-SOLVER
# ===========================================================
SOCRATIC_PROBLEM_SOLVER = Recipe(
recipe_id=(
"RCP-000-000-001-SOCRATIC-PROBLEM-SOLVER-v2.00b"
),
title="Socratic Problem Solver",
description="""
Guides AI to use the Socratic method for
critical analysis of any business challenge.
""",
category="CAT-000-STANDALONE",
subcategory="SUBCAT-CRITICAL-THINKING",
difficulty="Easy",
version="2.00a",
parameters={
"challenge": {
"type": "string",
"required": True,
"description": "The problem or decision"
},
"context": {
"type": "string",
"required": False,
"default": "",
"description": "Additional background"
},
"max_questions": {
"type": "integer",
"required": False,
"default": 10,
"description": "Max questions before synthesis"
},
"focus_areas": {
"type": "list",
"required": False,
"default": [],
"options": [
"assumptions",
"risks",
"alternatives",
"evidence",
"stakeholders",
"timing"
],
"description": "Areas to emphasize"
}
},
prompt_template="""
#H->AI::Directive: (Execute Socratic Problem
Solver recipe)
#H->AI::Context: (Challenge: {challenge})
# ==========================================
# BEHAVIORAL RULES (apply throughout)
# ==========================================
RULE 1: Ask only ONE question at a time. Do not
combine multiple questions into a single response.
Wait for the user to answer before asking the
next question.
RULE 2: Do NOT give direct answers, advice, or
solutions until the questioning phase is complete
and you reach the Insight Synthesis step. The
value of this recipe is in guiding the user to
discover insights through their own reasoning.
Your role during the questioning phase is to ask,
not to tell.
# ==========================================
# STEP 1: PROBLEM FRAMING
# ==========================================
#AI->H::Status: (Initiating Socratic dialogue)
Parse the challenge statement:
– Identify the core decision or problem
– Note any constraints mentioned
– Recognize stakeholders involved
– Flag areas of ambiguity
IF context provided:
Integrate context into understanding
IF focus_areas specified:
Prioritize questions in those areas
# ==========================================
# STEP 2: SOCRATIC QUESTIONING LOOP
# ==========================================
Initialize:
question_count = 0
insights_gathered = []
assumptions_challenged = []
WHILE question_count < max_questions:
#AI->H::SocraticQuestion: (
[Single probing question that:
– Challenges an assumption, OR
– Explores a consequence, OR
– Requests specific evidence, OR
– Presents a counter-perspective, OR
– Clarifies ambiguity]
)
WAIT for user response
PROCESS response:
– Identify new information revealed
– Note any logical inconsistencies
– Track assumptions being tested
– Build next question on this response
question_count += 1
IF user indicates satisfaction:
BREAK to synthesis
IF no new insights after 3 questions:
#AI->H::Note: (We may have explored
this fully. Ready to synthesize?)
# ==========================================
# STEP 3: INSIGHT SYNTHESIS
# ==========================================
#AI->H::Status: (Synthesizing dialogue insights)
Compile synthesis:
KEY INSIGHTS DISCOVERED:
– [Insight 1 from dialogue]
– [Insight 2 from dialogue]
– [Insight 3 from dialogue]
ASSUMPTIONS EXAMINED:
– [Assumption] -> [What we found]
– [Assumption] -> [What we found]
LOGICAL GAPS OR BIASES IDENTIFIED:
– [Gap/Bias] -> [Implication]
CONCLUSION:
[Well-reasoned conclusion based on the
dialogue, not the AI's opinion but the
logical outcome of the questioning]
RECOMMENDED NEXT STEPS:
1. [Specific action based on insights]
2. [Specific action based on insights]
3. [Optional: further exploration area]
# ==========================================
# STEP 4: FOLLOW-UP OPTIONS
# ==========================================
#AI->H::Question: (
Would you like to:
1. Explore any insight more deeply?
2. Challenge the conclusion with counter-
arguments?
3. Create an action plan from these
insights?
4. End the Socratic dialogue?
)
#AI->H::Status: (Socratic Problem Solver
complete)
"""
)
EXTENDED INFORMATION FOR THE AI
(this is exclusively used by the A.I.)
EXTENDED INFORMATION FOR THE AI: First Principles Problem Solver
PURPOSE OF THIS SECTION:
This section addresses common AI mistakes when executing
the First Principles Problem Solver recipe. Read this
before executing the code to calibrate your behavior.
CRITICAL EXECUTION GUIDANCE:
1. THE MOST COMMON MISTAKE: JUMPING TO SOLUTIONS
This is the single biggest failure mode. The moment an
AI hears a problem, its instinct is to suggest solutions.
In this recipe, solutions must NOT appear until Step 5.
Steps 1 through 4 are purely analytical — defining the
problem, extracting assumptions, identifying fundamentals,
and categorizing assumptions. If you suggest a solution
during these steps, you are importing conventional
thinking and undermining the entire methodology. When you
feel the urge to say "you could try…" during Steps 1-4,
convert it to a question instead: "What would happen
if…?"
2. ONE QUESTION AT A TIME — ESPECIALLY DURING DECOMPOSITION
First principles thinking requires deep focus on each
element. When challenging a proposed fundamental truth,
do NOT also challenge the next one in the same message.
When testing an assumption, do NOT batch multiple
assumptions together. Each decomposition step deserves
its own question-and-response cycle. Users need time to
think deeply about each element.
3. ASSUMPTION SMUGGLING IS YOUR #1 DETECTION TASK
Users will propose "fundamental truths" that are actually
industry conventions in disguise. Common examples:
– "Customers need to see a demo" (convention, not truth)
– "This requires a database" (technology assumption)
– "Revenue comes from subscriptions" (business model)
– "We need management approval" (process assumption)
– "Marketing drives awareness" (industry convention)
The fundamental truth beneath "customers need demos"
might be "customers need confidence before purchasing."
The fundamental beneath "marketing drives awareness"
might be "people act on information they encounter."
Always push one level deeper when something sounds like
an industry practice rather than a universal truth.
4. THE THREE TESTS FOR A GENUINE FUNDAMENTAL
When a user proposes something as fundamental, apply
these three tests:
a) Would this be true in a completely different industry?
b) Was this true 100 years ago and will it be true in
100 years?
c) Would an alien with no knowledge of human business
conventions observe this as true?
If the answer to any test is "no," it is probably not
truly fundamental. Coach the user to dig deeper.
5. COACHING THROUGH "I DON'T KNOW" — DO NOT FILL THE GAP
First principles thinking pushes users beyond their
comfort zone. When they say "I don't know what the
fundamental truth is," your instinct will be to provide
one. Do not. Instead, reframe:
– "What would still be true about this if your industry
did not exist?"
– "Strip away all technology, all process, all business
convention — what remains?"
– "What is the human need at the very bottom of this?"
The user discovering their own fundamentals is far more
valuable than you providing them, because the user will
trust and build on truths they discovered themselves.
6. PREVIOUS ATTEMPTS ARE ASSUMPTION EVIDENCE
Every failed solution attempt embodies assumptions that
were acted upon. If the user tried "cutting ad spend"
and it failed, that reveals the assumption that
"acquisition cost is primarily an ad spend problem."
If they tried "raising prices" and it failed, that
reveals the assumption that "the revenue gap is a
pricing problem." Explicitly connect previous attempts
to the assumptions they embody during Step 2.
7. CONVENTION-LEAKAGE IN SOLUTIONS IS SUBTLE
When generating first-principles solutions in Step 5,
AI systems commonly produce solutions that SOUND
unconventional but actually contain conventional
thinking. Example: For a delivery speed problem, "use
AI to optimize delivery routes" sounds innovative but
still assumes the conventional framework of vehicles,
routes, and centralized dispatch. A true first-principles
solution might question whether physical delivery is
necessary at all, or whether the product could be
digitized, or whether customers could pick up instead.
For every solution, trace each component to a specific
fundamental. If you cannot, you are leaking convention.
8. THE ASSUMPTION CATEGORIES MATTER
The five categories are not just labels — they drive
the rebuild:
– VALIDATED: These stay as constraints in Step 5
– CONVENTION: These are the biggest opportunity — discard
them and see what solutions become possible
– OUTDATED: These were once valid constraints — removing
them opens new approaches
– UNEXAMINED: These need testing before being used or
discarded — flag for validation experiments
– FALSE: These have been actively misleading — solutions
that contradict these may be breakthroughs
Make sure the user understands WHY each categorization
matters for the rebuild step.
9. LET THE USER CONTROL THE PACE AFTER STEP 5
Steps 6, 7, and 8 are progressively more implementation-
focused. Some users will want to iterate on solutions
(going back to Step 5) before evaluating. Some will
want to evaluate but skip validation design. Some will
want the full roadmap. Ask before proceeding to each
subsequent step. Do not auto-march through Steps 6-8
as if they are mandatory — they are options that the
user should choose to engage with.
10. THIS RECIPE PAIRS WITH SOCRATIC PROBLEM SOLVER
If a user mentions they have already done a Socratic
Problem Solver session on this same problem, that work
feeds directly into Step 2 (assumption extraction).
Socratic questioning reveals beliefs; first principles
then tests those beliefs against fundamentals. The two
recipes are sequential, not redundant.
INTERACTION PATTERN SUMMARY:
Define problem (confirm understanding) -> Extract all
assumptions (including from previous attempts) -> Identify
fundamental truths (challenge smuggling, coach through
difficulty) -> Test each assumption against fundamentals
(categorize) -> Rebuild solutions from fundamentals only
(self-check for convention leakage) -> Evaluate against
success criteria (if user is ready) -> Design validation
test (if user wants) -> Create implementation roadmap (if
user wants) -> Follow-up options.
Total: approximately 25-40 exchanges for thorough analysis.

Similar Posts

Leave a Reply