MVP Design

Objective

Core Principles

• Default to read from and write to the

  opc-doc/

  directory under the current working directory
• In teaching mode, first explain that MVP is not a "crude product", but "minimum validation"
• Default to asking only one question at a time; if several questions are very light and closely related to each other, you can merge them into 2 to 3 questions
• Default to providing 3 MVP solutions, plus an additional

  4. I have my own plan

  option
• Write formal results only after user confirmation
• Do not give direct recommendation conclusions, only provide solution analysis
• Only complete "what to validate, what minimal form to use for validation" at this stage, do not enter content creation or delivery details

Stage Boundaries

What to do at this step

• Confirm the highest-priority assumption that needs to be validated
• Select the minimum validation form (service-first / content validation / tool prototype and other categories)
• Clarify success criteria and MVP boundaries

What not to do at this step (the following belong to subsequent stages, do not enter in advance)

• ❌ Do not write specific content topics, copy or posts (belongs to opc-asset-ops)
• ❌ Do not design the complete conversion path (belongs to opc-conversion-loop)
• ❌ Do not design delivery SOP or operation details (belongs to opc-asset-ops)

"These execution details will be handled in the conversion closed loop and asset precipitation stages. Let's confirm the framework of the validation path first."

Mandatory Completion Items for This Step

1. Clarify the highest-priority assumption to be validated currently
2. Clarify the minimum validation form
3. Clarify success criteria
4. Clarify MVP boundaries
5. Clarify human-AI division of labor

Priority Confirmation Order

1. Highest-priority assumption to validate
2. Minimum validation form
3. Success criteria
4. MVP boundaries
5. Human-AI division of labor

Completion Criteria

• An executable MVP plan has been formed
• The user has confirmed the current main validation path

What to Explain at This Step

• The role of MVP is to validate assumptions
• More features are not always better
• One-person companies are more suitable for running through the minimum closed loop first

Input

• opc-doc/outputs/04-business-model/risky-assumptions.md

• opc-doc/outputs/05-opportunity-score/selected-opportunity.json

opc-business-model-design

opc-opportunity-score

Execution Steps

1. Explain the role of this step
2. Default to asking only one question at a time; if several questions are very light and closely related to each other, you can merge them into 2 to 3, for example:
   • Which assumption do you want to validate first most?
   • Would you prefer to validate with service, content or tool?
3. Give brief feedback after each round of answers
4. Generate 3 MVP solutions, for example:
   • Service-first version
   • Content validation version
   • Tool prototype version
5. Explain what each solution validates, what scenarios it is suitable for, advantages and costs
6. Add

   4. I have my own plan

   by default
7. Let users choose, combine, modify, or directly propose their own version
8. Write the formal result only after user confirmation

Output

1. Explanation of this step
2. Summary of the assumption to be validated currently
3. 3 MVP solutions +

   4. I have my own plan

4. Applicable scenarios, advantages and costs of each solution
5. Ask the user to confirm or modify

Persistence Checkpoint (must be completed at this stage, cannot be skipped)

• opc-doc/outputs/06-mvp-design/mvp-spec.md

  (validation assumption + minimum validation form + MVP boundary)

• opc-doc/outputs/06-mvp-design/experiment-plan.md

  (success criteria + validation cycle)

• opc-doc/outputs/06-mvp-design/human-ai-split.md

  (human vs AI division of labor description)

• opc-doc/state/current-stage.json

  (write:

  {"stage": "06-mvp-design", "status": "completed", "next_stage": "07-conversion-loop", "summary": "One-sentence MVP core"}

  )

• opc-doc/state/assumptions.json

  (update the status of validated/pending assumptions)

"✅ MVP plan has been saved. The next conversation can continue from the conversion closed loop."

opc-conversion-loop

When to Call Other Skills

opc-conversion-loop

Exception Handling

• If the user wants to validate too many things at once, you must help him narrow down to a single main validation goal
• If there is no clearly selected direction in the context, do not enter MVP design