SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsopc-mvp-designer

opc-mvp-designer

Agents & models

View repository

Updated 10-15 21:36

About this skill

MVP Design

Goal

Help the user determine "what to validate first and with what minimal form to validate it," rather than directly deciding on a product for the user.

Core Principles

  • By default, read and write opc-doc/
  • In teaching mode, first explain that an MVP is not a "crude product" but "minimal validation"
  • By default, ask only one question at a time; if several questions are all very light and closely related to each other, they can be combined into 2 to 3
  • By default, provide 3 MVP options, plus 4. 我有自己的方案
  • Write the formal results only after the user confirms
  • Do not directly give a recommended conclusion; only analyze the options
  • At this stage, only do "what to validate and with what minimal form to validate it"; do not enter content creation or delivery details

Boundaries of This Stage

What This Step Does

  • Confirm the highest-priority hypothesis that needs to be validated
  • Choose the minimal validation form (categories such as service-first / content validation / tool prototype, etc.)
  • Clarify the success criteria and MVP boundaries

What This Step Does Not Do (the following belong to later stages; do not enter them early)

  • ❌ 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 SOPs or operational details (belongs to opc-asset-ops)

Boundary-crossing detection: If execution topics such as "what to write in the first post," "how exactly to do this validation," or "how to write the copy" appear, record them first, then say:

"These execution details will be handled in the conversion loop and asset accumulation stages. For now, let's first confirm the framework of the validation path."

What This Step Must Complete

  1. Clarify the hypothesis that currently needs to be validated first
  2. Clarify the minimal validation form
  3. Clarify the success criteria
  4. Clarify the MVP boundaries
  5. Clarify the human-machine division of labor

Priority Confirmation Order

  1. The highest-priority hypothesis to validate
  2. Minimal validation form
  3. Success criteria
  4. MVP boundaries
  5. Human-machine division of labor

Completion Criteria

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

What This Step Needs to Explain

In teaching mode, first explain:

  • The role of an MVP is to validate hypotheses
  • It is not that the more features, the better
  • A one-person company is better suited to first getting a minimal loop running

Input

Read first:

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

If the dependencies are incomplete, first suggest going back to opc-business-model-design。

Execution Steps

  1. Explain the role of this step
  2. By default, ask only one question at a time; if several questions are all very light and closely related to each other, they can be combined into 2 to 3, for example:
    • Which hypothesis do you most want to validate first?
    • Would you rather validate with a service, content, or a tool?
  3. After each round of answers, give brief feedback
  4. Generate 3 MVP options, for example:
    • Service-first version
    • Content validation version
    • Tool prototype version
  5. Each option explains what it validates, what situations it suits, its advantages, and its costs
  6. By default, add 4. 我有自己的方案
  7. Let the user choose, combine, modify, or directly propose their own version
  8. After the user confirms, then write the formal result

Output

The dialogue layer must include:

  1. Explanation of this step
  2. Summary of the hypothesis to be verified currently
  3. 3 MVP options + 4. 我有自己的方案
  4. Applicable situations, advantages, and costs of each option
  5. Ask the user to confirm or modify

Persistence checkpoint (the stage must be completed, cannot be skipped)

After the user explicitly confirms the MVP option,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 dialogue does not count as persistence.

Write files:

  • opc-doc/outputs/06-mvp-design/mvp-spec.md(verification hypothesis + minimum verification form + MVP boundary)
  • opc-doc/outputs/06-mvp-design/experiment-plan.md(success criteria + verification cycle)
  • opc-doc/outputs/06-mvp-design/human-ai-split.md(explanation of human vs AI division of labor)

Update status file:

  • opc-doc/state/current-stage.json(write:{"stage": "06-mvp-design", "status": "completed", "next_stage": "07-conversion-loop", "summary": "一句话 MVP 核心"}）
  • opc-doc/state/assumptions.json(update verified/to-be-verified hypothesis status)

After persistence is complete, inform the user in the dialogue:

"✅ MVP option has been saved. The next dialogue can continue from the conversion loop."

Only after persistence is complete may you prompt to proceed to opc-conversion-loop。

When to call other skills

Only after the user confirms the MVP option, enter opc-conversion-loop。

Exception handling

  • If the user wants to verify too many things at once, you must help them narrow it down to a single primary verification goal
  • If the context has not clearly selected a direction, do not enter MVP design