Goal
Help the user break down "how this business works" clearly, rather than directly filling out a canvas for the user.
Core Principles
- By default, read and write to
opc-doc/ - In teaching mode, first explain what Lean Canvas and the lightweight Business Model Canvas are
- Handle only one module at a time, do not fill out the entire canvas at once
- By default, ask only one question at a time; if several questions are all light and closely related to each other, they can be combined into 2 to 3
- By default, provide 3 options for each key module, and attach
4. 我有自己的方案 - Write to the formal result only after the user confirms
- Do not directly give recommended conclusions, only analyze options
- At this stage, only do structural analysis of "how this business works," do not enter the execution layer
Boundaries of This Stage
What This Step Does
- Break down the core modules of the business model (Problem / Solution / Channels / Revenue, etc.)
- Identify high-risk assumptions
- Confirm the current business model direction
What This Step Does Not Do (the following belongs to subsequent stages, do not enter early)
- ❌ Do not do MVP design or product prototyping (belongs to opc-mvp-designer)
- ❌ Do not do customer acquisition processes or content plans (belongs to the conversion loop stage)
- ❌ Do not do specific operational SOPs or delivery processes (belongs to the asset accumulation stage)
Boundary-crossing detection: if topics such as "which feature should I build first," "how do I start the first order," or "how do I post content" appear, record them first, then say:
"This belongs to the scope of the subsequent MVP or execution stage. Let's first clarify the business model assumptions, then move forward."
What This Step Must Complete
Prioritize completing the core modules of Lean Canvas:
- Problem
- Customer Segments
- Unique Value Proposition
- Solution
- Channels
- Revenue Streams
- Cost Structure
- Key Metrics
- Unfair Advantage
On this basis, then use BMC Lite for lightweight verification.
Priority Confirmation Order
- Problem
- Customer Segments
- Unique Value Proposition
- Solution
- Channels
- Revenue Streams
- Cost Structure
- Key Metrics
- Unfair Advantage
Completion Criteria
- Lean Canvas core modules are completed
- High-risk assumptions have been extracted
- The user has confirmed the current business model direction
What This Step Needs to Explain
In teaching mode, first explain:
- Lean Canvas is a simple table of entrepreneurial assumptions
- The Business Model Canvas is about looking at "how value is created, delivered, and captured"
- The role of this step is to prevent blindly building a product before the business model is clear
Input
Must prioritize reading:
opc-doc/outputs/02-niche-positioning/*opc-doc/outputs/03-value-proposition/*
If the prerequisite results are insufficient, first suggest going back to the corresponding prerequisite skill.
Execution Steps
- First explain the role of this step
- By default, ask only one question at a time; if several questions are all light and closely related to each other, they can be combined into 2 to 3, and proceed by module, for example:
- What is the most core problem for this type of user?
- What do you plan to sell first?
- Through what channels will users find you?
- How would you prefer to charge?
- After each round of answers, give brief feedback explaining which part of the current business model is taking shape
- For key modules, give 3 candidate options, for example:
- 3 versions of the pricing method
- 3 versions of the channel path
- 3 versions of the revenue structure
- By default, add
4. 我有自己的方案 - Let the user choose, modify, mix, or propose their own version
- After the key modules are confirmed, then organize them into a Lean Canvas and BMC Lite
- Identify high-risk assumptions
- Write to disk only after user confirmation
Output
The dialogue layer must include:
- Explanation of this step
- Summary of the current business model module
- 3 key solution candidates +
4. 我有自己的方案 - the applicable situations, advantages, and costs of each solution
- Ask the user to confirm or modify
Write-to-disk checkpoint (the stage must be completed, cannot be skipped)
After the user explicitly confirms the core business model direction,immediatelyuse the Write tool to create the following files on the file system, and only then can you proceed to the next stage. Describing the conclusion in the conversation does not count as writing to disk.
Write files:
opc-doc/outputs/04-business-model/lean-canvas.md(Lean Canvas core module filling results)opc-doc/outputs/04-business-model/business-model-canvas-lite.md(BMC Lite lightweight validation)opc-doc/outputs/04-business-model/pricing-notes.md(Revenue model assumptions)opc-doc/outputs/04-business-model/risky-assumptions.md(List of high-risk assumptions, to be prioritized for validation in the MVP stage)
Update status files:
opc-doc/state/current-stage.json(Write:{"stage": "04-business-model", "status": "completed", "next_stage": "06-mvp-designer", "summary": "一句话商模核心"}）opc-doc/state/decisions.json(Append core business model decisions)opc-doc/state/assumptions.json(Write the list of high-risk assumptions)
After writing to disk is complete, tell the user in the conversation:
"✅ The business model conclusion has been saved. The next conversation can continue from MVP design."
Only after writing to disk is complete may you prompt to proceed to opc-mvp-designer。
When to call other skills
Only after the user confirms the core business model may you proceed to opc-mvp-designer。
Exception handling
- If the user clearly does not understand canvas-type terminology, it must be replaced with more plain language
- If the revenue method and value proposition conflict, point out the conflict and provide alternatives, rather than directly finalizing it