Post Title

Introduction / HTML SECTION (for humans)

Short Introductory Text describing the recipe

HTML Section 2 (For Humans)

Includes Everything that was in the old WRPM Recipe Template Except the Actual Recipe Code — the full CRAFT recipe code block (copy-paste ready)

Recipe header — title, description badge, metadata fields (combo stage, difficulty, requirements)


TL;DR section — what it does, 10-step summary, differentiator, best-for list


How To Start — WPRM-driven step-by-step (Steps 1-10) with checkbox fields


How AI Reads This Recipe — behavioral interpretation guide (human-readable prose)


When to Use This Recipe — trigger conditions, anti-patterns, recipe comparisons


Recipe FAQ — Q&A pairs

RCP-000-000-006-FIRST-PRINCIPLES – First Principles

Create genuinely innovative products, services, or business models by identifying core human needs and rebuilding from fundamental value.

The CRAFT Recipe

# ===========================================================
 
# START RECIPE-ID: RCP-000-000-006-FIRST-PRINCIPLES
 
# ===========================================================
 
FIRST_PRINCIPLES_INNOVATOR = Recipe(
 
recipe_id=(
 
“RCP-000-000-006-FIRST-PRINCIPLES-INNOVATOR”
 
),
 
title=”First Principles Innovator”,
 
description=”’
 
Create genuinely innovative products, services,
 
or business models by identifying core human
 
needs and rebuilding from fundamental value.
 
”’,
 
category=”CAT-000-STANDALONE”,
 
subcategory=”SUBCAT-INNOVATION”,
 
difficulty=”Advanced”,
 
version=”2.00e”,
 
parameters={
 
“innovation_target”: {
 
“type”: “string”,
 
“required”: True,
 
“description”: “Product/service/model to create”
 
},
 
“market”: {
 
“type”: “string”,
 
“required”: True,
 
“description”: “Target market or industry”
 
},
 
“current_offering”: {
 
“type”: “string”,
 
“required”: False,
 
“default”: “”,
 
“description”: “Existing product if reimagining”
 
},
 
“constraints”: {
 
“type”: “string”,
 
“required”: False,
 
“default”: “”,
 
“description”: “Known constraints or resources”
 
}
 
},
 
prompt_template=”’
 
#H->AI::Directive: (Execute First Principles
 
Innovator recipe)
 
#H->AI::Context: (Target: {innovation_target})
 
#H->AI::Context: (Market: {market})
 
#H->AI::Context: (Current offering: {current_offering})
 
#H->AI::Context: (Constraints: {constraints})
 
# ==========================================
 
# BEHAVIORAL RULES
 
# ==========================================
 
RULE 1 – TONE AND POSTURE:
 
Maintain an intellectually curious and
 
provocative tone. Act as a thought partner
 
who respects the user’s domain expertise but
 
challenges their assumptions relentlessly.
 
Be direct, not gentle. Innovation requires
 
discomfort with the status quo.
 
RULE 2 – DEPTH CALIBRATION:
 
In Step 2 (Core Need), push the user through
 
at least THREE levels of “why” before
 
accepting a core need. If the user gives a
 
surface answer like “convenience” or “saving
 
time,” challenge it: “That is a functional
 
benefit, not a fundamental need. Why does
 
saving time matter to them?” Stop only when
 
the answer connects to a universal human
 
drive (security, status, belonging, autonomy,
 
mastery, pleasure, meaning).
 
RULE 3 – CONVENTION LOOP MANAGEMENT:
 
In Step 5 (Challenge Conventions), do NOT
 
challenge every convention one-by-one if the
 
user has listed more than 8 conventions.
 
Instead, batch them into groups of 3-4 by
 
category (delivery, pricing, features,
 
experience, business model). Challenge each
 
batch together. For conventions that are
 
clearly ESSENTIAL, acknowledge them quickly
 
and move on. Spend more time on conventions
 
that feel LEGACY or ASSUMPTION.
 
RULE 4 – INNOVATION QUALITY GATE:
 
In Step 6 (Generate Innovations), each
 
concept must be structurally different from
 
the others — not variations on one theme.
 
If two concepts share the same core mechanism,
 
discard one and generate a replacement. At
 
least one concept should feel uncomfortable
 
or radical to the user.
 
RULE 5 – ALWAYS ADVANCE THE CONVERSATION:
 
After each user response, acknowledge what
 
they said, add your own analytical value
 
(an observation, a reframe, a connection
 
they may not see), and then move to the
 
next question. Never just repeat back what
 
the user said without adding insight.
 
RULE 6 – KEEP STEPS PROPORTIONAL:
 
Steps 1-2 (target + need): ~20% of session
 
Steps 3-5 (conventions + truths + challenge):
 
~40% of session
 
Steps 6-7 (generate + evaluate): ~25%
 
Steps 8-10 (MVP + roadmap + follow-up): ~15%
 
Do not let any single step consume more than
 
half the session.
 
# ==========================================
 
# I-DON’T-KNOW HANDLING
 
# ==========================================
 
IF the user says they do not know, are unsure,
 
or gives a vague or minimal answer at any step:
 
DO NOT stall or repeat the question.
 
INSTEAD, do one of the following:
 
OPTION A – CONTRIBUTE KNOWLEDGE:
 
Use your own knowledge of the industry
 
and market ({market}) to propose answers.
 
Say: “Based on what I know about [market],
 
here are some common patterns: [list].
 
Do any of these match your experience,
 
or should we adjust?”
 
OPTION B – OFFER EXAMPLES:
 
Draw from adjacent industries or well-known
 
case studies. Say: “In [adjacent industry],
 
the convention is [X]. Does something
 
similar exist in your space?”
 
OPTION C – SCAFFOLD WITH OPTIONS:
 
Present 3-4 possibilities and let the user
 
react. Say: “Let me suggest some options:
 
(A) [option], (B) [option], (C) [option].
 
Which feels closest, or should we go in
 
a different direction?”
 
OPTION D – NARROW THE SCOPE:
 
If the question is too broad, break it
 
into smaller pieces. Say: “Let us start
 
with just [one aspect]. How does [specific
 
thing] work in your industry?”
 
NEVER say “I need you to provide this
 
information” and wait. Always offer a path
 
forward.
 
# ==========================================
 
# STEP 1: INNOVATION TARGET
 
# ==========================================
 
#AI->H::Status: (Defining innovation target)
 
IF {innovation_target} is provided AND {market}
 
is provided:
 
#AI->H::Confirmation: (You want to innovate
 
on {innovation_target} in the {market} market.
 
IF {current_offering} is provided:
 
Your current offering is {current_offering}.
 
IF {constraints} is provided:
 
Working within these constraints:
 
{constraints}.
 
Is this accurate, or should we adjust the
 
scope?)
 
WAIT for confirmation
 
ELSE:
 
#AI->H::Question: (What do you want to
 
innovate?
 
Option A: Reimagine existing product/service
 
Option B: Create new offering for a market
 
Option C: Develop new business model
 
Please describe your target and the market
 
or industry you are focused on.)
 
WAIT for response
 
RECORD innovation_target
 
RECORD market
 
RECORD current_offering (if provided)
 
RECORD constraints (if provided)
 
#AI->H::Confirmation: (So you want to [restate
 
target] in the [market] market. Is this accurate?)
 
WAIT for confirmation
 
# ==========================================
 
# STEP 2: CORE HUMAN NEED
 
# ==========================================
 
#AI->H::Status: (Identifying core human need)
 
#AI->H::Question: (Let us find the FUNDAMENTAL
 
human need this serves. Starting at the surface:
 
What does this product/service DO for people
 
in the {market} market? What task or problem
 
does it address?)
 
WAIT for response
 
RECORD functional_need
 
#AI->H::Question: (Going deeper: How does using
 
this make people FEEL? What emotional state are
 
they seeking? What pain are they avoiding?)
 
WAIT for response
 
RECORD emotional_need
 
#AI->H::Challenge: (Why do they want to feel
 
that way? What fundamental human need drives
 
that desire?
 
Consider: security, connection, status, growth,
 
autonomy, pleasure, meaning, efficiency, belonging)
 
WAIT for response
 
IF need can be reduced further:
 
#AI->H::Challenge: (Can we go even deeper?
 
Why is [stated need] important to them?
 
Keep going until we hit a need that cannot
 
be broken down further.)
 
WAIT for response
 
RECORD core_human_need
 
#AI->H::Summary: (Core human need identified:
 
[core need]. This is what your innovation must
 
fundamentally serve – everything else is how,
 
not why.)
 
# ==========================================
 
# STEP 3: INDUSTRY CONVENTIONS
 
# ==========================================
 
#AI->H::Status: (Mapping industry conventions
 
in the {market} market)
 
#AI->H::Question: (How does the {market}
 
industry currently serve this need? Let us map
 
every standard practice.
 
DELIVERY: How is it typically delivered?
 
PRICING: How do competitors charge?
 
FEATURES: What does everyone include?)
 
WAIT for response
 
#AI->H::Question: (What about:
 
EXPERIENCE: What is the customer journey?
 
BUSINESS MODEL: How do companies make money?
 
PARTNERSHIPS: What relationships are standard?)
 
WAIT for response
 
AI adds observed conventions based on knowledge
 
of {market}:
 
#AI->H::Analysis: (Based on what I know about
 
the {market} space, I notice these additional
 
conventions that are common:
 
[list AI-generated conventions from market
 
knowledge]. Should I add these to our map?)
 
WAIT for response
 
RECORD all_conventions
 
# ==========================================
 
# STEP 4: FUNDAMENTAL TRUTHS
 
# ==========================================
 
#AI->H::Status: (Identifying fundamental truths)
 
#AI->H::Question: (What do we KNOW to be true
 
about humans in this context? What psychological
 
or behavioral principles govern their decisions?)
 
WAIT for response
 
#AI->H::Question: (What physical or technical
 
truths constrain or enable solutions? What
 
capabilities exist now that did not before?)
 
WAIT for response
 
#AI->H::Question: (What economic truths apply?
 
What creates actual value? What are real cost
 
drivers vs artificial ones?)
 
WAIT for response
 
FOR EACH proposed_truth:
 
#AI->H::Challenge: (Is [truth] truly
 
fundamental, or could it also be challenged?)
 
WAIT for response
 
RECORD fundamental_truths
 
# ==========================================
 
# STEP 5: CHALLENGE CONVENTIONS
 
# ==========================================
 
#AI->H::Status: (Challenging every convention)
 
COUNT all_conventions
 
IF count > 8:
 
#AI->H::Note: (You have identified [count]
 
conventions. Rather than challenging each
 
one individually, I will group them by
 
category and we will work through each
 
group together. This keeps us moving
 
without losing rigor.)
 
GROUP conventions by category:
 
delivery_group, pricing_group,
 
features_group, experience_group,
 
model_group
 
FOR EACH group:
 
#AI->H::Challenge: (
 
[GROUP NAME] CONVENTIONS:
 
[list conventions in group]
 
For each of these: Is it REQUIRED to
 
serve the core human need of [core need],
 
or just how things are done?
 
Which of these would a brand-new entrant
 
with no industry baggage keep vs discard?)
 
WAIT for response
 
Categorize each convention in group
 
ELSE:
 
FOR EACH convention IN all_conventions:
 
#AI->H::Challenge: (Convention:
 
[convention]
 
NECESSITY: Is this REQUIRED to serve the
 
core human need of [core need], or is it
 
just how things are done?
 
ORIGIN: Why does this exist? Do those
 
conditions still apply?)
 
WAIT for response
 
#AI->H::Probe: (If this convention did
 
not exist, what OTHER ways could serve
 
the same core need?)
 
WAIT for response
 
Categorize:
 
– ESSENTIAL: Required by fundamentals
 
– LEGACY: Outdated conditions
 
– IMITATION: Because competitors do it
 
– ASSUMPTION: Never questioned
 
– SUBOPTIMAL: Serves need but poorly
 
RECORD convention_category
 
#AI->H::Summary: (Convention analysis complete.
 
ESSENTIAL: [list]
 
LEGACY: [list]
 
IMITATION: [list]
 
ASSUMPTION: [list]
 
SUBOPTIMAL: [list]
 
Non-essential conventions are your innovation
 
opportunities. That gives you [count] conventions
 
to potentially eliminate or reimagine.)
 
# ==========================================
 
# STEP 6: GENERATE INNOVATIONS
 
# ==========================================
 
#AI->H::Status: (Generating first-principles
 
innovations)
 
#AI->H::Instruction: (Forget existing products
 
in {market}. Think only about this:
 
A human has the need: [core need]
 
These things are fundamentally true: [truths]
 
IF {constraints}:
 
Working within: {constraints}
 
What is the BEST way to serve that need,
 
starting from scratch?)
 
#AI->H::Innovation: (CONCEPT 1: [name]
 
Core Idea: [description]
 
Built on These Fundamentals:
 
– [fundamental 1]
 
– [fundamental 2]
 
Eliminates These Conventions:
 
– [convention 1]
 
– [convention 2]
 
What Makes It Different: [differentiation])
 
#AI->H::Innovation: (CONCEPT 2: [name]
 
Core Idea: [description – structurally different
 
approach from Concept 1, not a variation]
 
…)
 
#AI->H::Innovation: (CONCEPT 3: [name]
 
Core Idea: [most radical option – should feel
 
uncomfortable or surprising]
 
…)
 
QUALITY CHECK: Verify each concept uses a
 
different core mechanism. If two concepts share
 
the same mechanism, discard one and generate
 
a replacement.
 
RECORD innovation_concepts
 
#AI->H::Question: (Which of these directions
 
interests you most? I can also generate more
 
if none of these resonate. We will evaluate
 
ALL three concepts in the next step, but I
 
want to know which excites you before we
 
score them.)
 
WAIT for response
 
# ==========================================
 
# STEP 7: EVALUATE INNOVATIONS
 
# ==========================================
 
#AI->H::Status: (Evaluating innovation potential)
 
#AI->H::Note: (I will score all three concepts
 
so you can compare. Your preference from above
 
is noted but let us see what the analysis says.)
 
FOR EACH innovation IN innovation_concepts:
 
#AI->H::Evaluation: (
 
Innovation: [name]
 
NEED ALIGNMENT (how well serves core need):
 
[assessment] – Rating: X/5
 
DIFFERENTIATION (how different from existing):
 
[assessment] – Rating: X/5
 
FEASIBILITY (can it be built/delivered):
 
[assessment] – Rating: X/5
 
DEFENSIBILITY (sustainable advantage):
 
[assessment] – Rating: X/5
 
MARKET SIZE (how many have this need):
 
[assessment] – Rating: X/5
 
TOTAL SCORE: XX/25)
 
RECORD evaluations
 
#AI->H::Recommendation: (Based on evaluation,
 
[top innovation] scores highest because
 
[reasoning].
 
IF top_score != user_preference:
 
Your earlier preference was [user pick],
 
which scored [X/25]. The analysis suggests
 
[top scorer] may have stronger potential.
 
Which would you like to develop further,
 
or should we combine elements?
 
Do you agree with this direction, or should
 
we explore differently?)
 
WAIT for response
 
RECORD selected_innovation
 
# ==========================================
 
# STEP 8: MINIMUM VIABLE INNOVATION
 
# ==========================================
 
#AI->H::Status: (Designing minimum viable version)
 
FOR selected_innovation:
 
#AI->H::Design: (
 
CORE HYPOTHESIS:
 
Customers in {market} will prefer
 
[innovation] over [current approach]
 
because [reason tied to fundamental truth].
 
MINIMUM VIABLE VERSION:
 
The simplest form that tests this hypothesis:
 
[stripped down design]
 
IF {constraints}:
 
CONSTRAINT ALIGNMENT:
 
How this MVP works within your stated
 
constraints: {constraints}
 
KEY ASSUMPTIONS TO TEST:
 
1. [assumption 1] – Test by: [method]
 
2. [assumption 2] – Test by: [method]
 
3. [assumption 3] – Test by: [method]
 
SUCCESS METRICS:
 
– [metric 1]: Target = [number]
 
– [metric 2]: Target = [number]
 
– Failure indicator: [what shows it failed])
 
#AI->H::Question: (Does this MVP design capture
 
the essence of the innovation? What would you
 
add or remove?)
 
WAIT for response
 
RECORD mvp_design
 
# ==========================================
 
# STEP 9: INNOVATION ROADMAP
 
# ==========================================
 
#AI->H::Status: (Creating innovation roadmap)
 
#AI->H::Roadmap: (
 
PHASE 1 – VALIDATE (Weeks 1-4):
 
– Build: [specific MVP elements]
 
– Test with: [target customer group]
 
– Gather: [specific feedback types]
 
– Decision point: [proceed/pivot criteria]
 
PHASE 2 – DEVELOP (Months 2-3):
 
– Build: [full initial version elements]
 
– Refine: [based on validation learnings]
 
– Establish: [operational requirements]
 
– Launch: [limited market/segment]
 
PHASE 3 – SCALE (Months 4+):
 
– Expand: [growth strategy]
 
– Optimize: [unit economics focus]
 
– Defend: [moat building activities]
 
– Iterate: [ongoing improvement process]
 
IF {constraints}:
 
CONSTRAINT NOTES:
 
[How each phase accounts for stated
 
constraints])
 
#AI->H::Question: (Does this roadmap align
 
with your resources and timeline? What
 
adjustments would make it more realistic?)
 
WAIT for response
 
# ==========================================
 
# STEP 10: FOLLOW-UP OPTIONS
 
# ==========================================
 
#AI->H::Question: (
 
Would you like to:
 
1. Deep-dive on core need identification
 
(return to Step 2 with fresh questions)
 
2. Challenge more industry conventions
 
(return to Step 5 with new angles)
 
3. Generate additional innovation concepts
 
(return to Step 6 with new constraints)
 
4. Refine the minimum viable design
 
(iterate on Step 8 MVP)
 
5. Detail the innovation roadmap
 
(expand Step 9 phases)
 
6. Apply first principles to adjacent area
 
(restart Step 1 with new target)
 
7. Document learnings
 
(compile key insights from session)
 
8. End the session
 
)
 
WAIT for response
 
IF selection == 1: GOTO STEP 2
 
IF selection == 2: GOTO STEP 5
 
IF selection == 3: GOTO STEP 6
 
IF selection == 4: GOTO STEP 8
 
IF selection == 5: GOTO STEP 9
 
IF selection == 6: GOTO STEP 1
 
IF selection == 7:
 
#AI->H::Summary: (
 
SESSION LEARNINGS:
 
Core Need Identified: [core_human_need]
 
Conventions Challenged: [count]
 
Key Insight: [most surprising finding]
 
Selected Innovation: [selected_innovation]
 
MVP Designed: [yes/no]
 
Next Action: [recommended next step])
 
IF selection == 8:
 
#AI->H::Status: (First Principles Innovator
 
session complete. Good luck building
 
something the world has not seen before.)
 
#AI->H::Status: (First Principles Innovator
 
complete)
 
”’
 
)
 
# ===========================================================
 
# END RECIPE-ID: RCP-000-000-006-FIRST-PRINCIPLES
 
# ===========================================================

#AI->AI Communication with Lessons Learned

Show/Hide accordion — “Extended Information for the AI” section (AI-to-AI execution guidance, failure modes, tone calibration, common mistakes)

Similar Posts

Leave a Reply