Back to Details

opc-mvp-designer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

MVP 设计

MVP Design

目标

Objective

帮助用户确定“最先验证什么、用什么最小形式去验证”，而不是替用户直接定一个产品。
Help users determine "what to validate first, and what minimal form to use for validation", instead of directly defining a product for the user.

核心原则

Core Principles

  • 默认读写当前工作目录下的 
    opc-doc/
  • 教学模式下先解释 MVP 不是“简陋产品”，而是“最小验证”
  • 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个
  • 默认给 3 个 MVP 方案，并附加 
    4. 我有自己的方案
  • 用户确认后再写入正式结果
  • 不直接给推荐结论，只做方案分析
  • 本阶段只做"验证什么、用什么最小形式验证"，不进入内容创作或交付细节
  • 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

  • 确认最优先需要验证的假设
  • 选定最小验证形式（服务先行 / 内容验证 / 工具原型等类别）
  • 明确成功标准和 MVP 边界
  • 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)

  • ❌ 不写具体内容选题、文案或帖子（属于 opc-asset-ops）
  • ❌ 不设计完整转化路径（属于 opc-conversion-loop）
  • ❌ 不设计交付 SOP 或运营细节（属于 opc-asset-ops）
越界检测：如果出现"第一篇帖子写什么""具体怎么做这次验证""文案怎么写"等执行话题，先记录，再说：
"这些执行细节会在转化闭环和资产沉淀阶段处理。现在先把验证路径的框架确认好。"
  • ❌ 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)
Cross-boundary detection: If execution topics such as "what to write for the first post", "how to conduct this validation specifically", "how to write the copy" appear, record them first, then say:
"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. 明确当前最先要验证的假设
  2. 明确最小验证形式
  3. 明确成功标准
  4. 明确 MVP 边界
  5. 明确人机分工
  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. 最优先验证的假设
  2. 最小验证形式
  3. 成功标准
  4. MVP 边界
  5. 人机分工
  1. Highest-priority assumption to validate
  2. Minimum validation form
  3. Success criteria
  4. MVP boundaries
  5. Human-AI division of labor

完成标准

Completion Criteria

  • 已形成可执行的 MVP 方案
  • 用户已确认当前主验证路径
  • An executable MVP plan has been formed
  • The user has confirmed the current main validation path

本步需要解释什么

What to Explain at This Step

教学模式下先解释：
  • MVP 的作用是验证假设
  • 不是功能越多越好
  • 一人公司更适合先跑通最小闭环
Explain first in teaching mode:
  • 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
。
Prioritize reading:
  • opc-doc/outputs/04-business-model/risky-assumptions.md
  • opc-doc/outputs/05-opportunity-score/selected-opportunity.json
If dependencies are incomplete, first suggest returning to 
opc-business-model-design
or 
opc-opportunity-score
.

执行步骤

Execution Steps

  1. 解释本步作用
  2. 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个，例如：
    • 你最想先验证的假设是哪一个？
    • 你更愿意用服务、内容还是工具来验证？
  3. 每轮回答后，给简短反馈
  4. 生成 3 个 MVP 方案，例如：
    • 服务先行版
    • 内容验证版
    • 工具原型版
  5. 每个方案说明验证什么、适合什么情况、优点和代价
  6. 默认增加 
    4. 我有自己的方案
  7. 让用户选择、组合、修改，或直接提出自己的版本
  8. 用户确认后，再写入正式结果
  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. 本步解释
  2. 当前要验证的假设摘要
  3. 3 个 MVP 方案 + 
    4. 我有自己的方案
  4. 每个方案的适用情况、优点和代价
  5. 请用户确认或修改
The conversation layer must include:
  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)

用户明确确认 MVP 方案后，立即使用 Write 工具在文件系统上创建以下文件，然后才能进入下一阶段。在对话中描述结论不等于落盘。
写入文件：
  • opc-doc/outputs/06-mvp-design/mvp-spec.md
    （验证假设 + 最小验证形式 + MVP 边界）
  • opc-doc/outputs/06-mvp-design/experiment-plan.md
    （成功标准 + 验证周期）
  • opc-doc/outputs/06-mvp-design/human-ai-split.md
    （人工 vs AI 分工说明）
更新状态文件：
  • opc-doc/state/current-stage.json
    （写入：
    {"stage": "06-mvp-design", "status": "completed", "next_stage": "07-conversion-loop", "summary": "一句话 MVP 核心"}
    ）
  • opc-doc/state/assumptions.json
    （更新已验证/待验证假设状态）
落盘完成后，在对话中告知用户：
"✅ MVP 方案已保存。下次对话可以从转化闭环继续。"
只有落盘完成后，才可以提示进入 
opc-conversion-loop
。
After the user explicitly confirms the MVP plan, immediately use the Write tool to create the following files on the file system before entering the next stage. Describing the conclusion in the conversation does not equal persistence.
Files to write:
  • 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)
Update status files:
  • 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)
After persistence is completed, inform the user in the conversation:
"✅ MVP plan has been saved. The next conversation can continue from the conversion closed loop."
Only after persistence is completed can you prompt to enter 
opc-conversion-loop
.

何时调用其他 skills

When to Call Other Skills

只有在用户确认 MVP 方案后，才进入 
opc-conversion-loop
。
Only after the user confirms the MVP plan, enter 
opc-conversion-loop
.

异常处理

Exception Handling

  • 如果用户想一次验证太多东西，必须帮助他收缩成单一主验证目标
  • 如果上下文没有明确选定方向，不进入 MVP 设计
  • 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