opc-mvp-designer

Original：🇨🇳 Chinese

Translated

Define the smallest viable experiment and MVP for a selected one-person company opportunity. Use when Codex needs to explain what MVP means when needed, verify prerequisites, ask one question at a time, present multiple MVP options, and write user-confirmed outputs into `opc-doc/`.

6installs

Sourceeasychen/opc-methodology

Added on2026-04-12

NPX Install

npx skill4agent add easychen/opc-methodology opc-mvp-designer

SKILL.md Content (Chinese)

View Translation Comparison →

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

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)

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

Clarify the highest-priority assumption to be validated currently
Clarify the minimum validation form
Clarify success criteria
Clarify MVP boundaries
Clarify human-AI division of labor

Priority Confirmation Order

Highest-priority assumption to validate
Minimum validation form
Success criteria
MVP boundaries
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

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

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

Explain the role of this step
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?
Give brief feedback after each round of answers
Generate 3 MVP solutions, for example:
- Service-first version
- Content validation version
- Tool prototype version
Explain what each solution validates, what scenarios it is suitable for, advantages and costs
Add
```
4. I have my own plan
```
by default
Let users choose, combine, modify, or directly propose their own version
Write the formal result only after user confirmation

Output

The conversation layer must include:

Explanation of this step
Summary of the assumption to be validated currently
3 MVP solutions +
```
4. I have my own plan
```
Applicable scenarios, advantages and costs of each solution
Ask the user to confirm or modify

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

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
.

When to Call Other Skills

Only after the user confirms the MVP plan, enter

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