opc-value-proposition

Value Proposition

Objective

Help users clarify "why this type of person should buy from you," and provide selectable value proposition options.

Core Principles

By default, read and write the opc-doc/
In teaching mode, first explain jobs, pains, gains
One type of customer segment corresponds to one type of value proposition
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 value proposition directions, and additionally 4. 我有自己的方案
Write to the formal result only after user confirmation
Do not directly give a recommended conclusion; only perform option analysis
At this stage, only do the structured analysis of "why buy from you"; do not enter script design or content creation

Boundaries of This Stage

What This Step Does

Break down the target user's Jobs / Pains / Gains (structured framework layer)
Analyze how your product/service corresponds to user needs (framework layer)
Generate 3 value proposition versions for the user to choose from (descriptive language, not promotional script)

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

❌ Do not write specific advertising copy or promotional scripts (belongs to the asset accumulation stage)
❌ Do not design content topics or post structures (belongs to the asset accumulation stage)
❌ Do not do pricing strategy or charging plans (belongs to the business model design stage)
❌ Do not design conversion paths or customer acquisition steps (belongs to the conversion loop stage)

Boundary Crossing Detection: If execution topics such as "how to write a title," "Xiaohongshu copy," "how to persuade users" appear, first record them, then say:

"These execution details are important, and we will handle them specifically in subsequent stages. For now, let's first confirm the logical framework of 'why buy from you.'"

What This Step Must Complete

Target customer segment confirmation
Customer Jobs
Pains
Gains
Products / Services
Pain Relievers
Gain Creators
Value proposition version comparison

Priority Confirmation Order

Target customer segment
Customer Jobs
Pains
Gains
Products / Services
Pain Relievers
Gain Creators
Value proposition version selection

Completion Criteria

The key modules of the value proposition canvas are complete
The user has confirmed the currently featured value proposition version

What This Step Needs to Explain

In teaching mode, first explain:

Jobs: what task the user wants to complete
Pains: the most painful obstacles the user faces when completing the task
Gains: the benefits the user ideally wants to obtain
Value proposition: how you plan to help this type of user complete the task better

Input

Must first read:

opc-doc/outputs/02-niche-positioning/segments.md
opc-doc/outputs/02-niche-positioning/target-segment.json
opc-doc/outputs/02-niche-positioning/positioning-statement.md

If these files are missing, first determine whether the current conversation has already clarified the target segment and positioning.

If not, first suggest calling opc-niche-positioning

Execution Steps

Explain the objective and terminology of this step
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:
- What result does this type of user most want to obtain?
- What is the most painful point for them right now?
- Why are they dissatisfied with the existing options?
After each round of answers, summarize the current understanding of jobs / pains / gains in plain language
Generate 3 value proposition versions, for example:
- Efficiency-improvement type
- Result-oriented type
- Risk-reducing type
Each version explains the applicable situation, advantages, and costs
By default, add 4. 我有自己的方案
Let users choose, combine, modify, or directly propose their own version
After the user confirms, then write it into the formal result

Output

The dialogue layer must include:

Explanation of this step
Summary of current jobs / pains / gains
3 value proposition candidates + 4. 我有自己的方案
The applicable situation, advantages, and costs of each option
Ask the user to confirm or modify

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

After the user explicitly confirms the main value proposition version,immediatelyuse the Write tool to create the following files on the file system, and only then can you proceed to the next phase. Describing the conclusion in the conversation does not count as persistence.

Write files:

opc-doc/outputs/03-value-proposition/value-proposition-canvas.md(Complete canvas of Jobs / Pains / Gains + Pain Relievers / Gain Creators)
opc-doc/outputs/03-value-proposition/segment-vp-matrix.md(Mapping between target customer segments × value propositions)
opc-doc/outputs/03-value-proposition/messaging.md(Confirmed main value proposition statement, framework level, not advertising copy)

Update status file:

opc-doc/state/current-stage.json(Write:{"stage": "03-value-proposition", "status": "completed", "next_stage": "04-business-model", "summary": "一句话价值主张核心"}）
opc-doc/state/decisions.json(Append the confirmed value proposition version)

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

"✅ The value proposition conclusion has been saved. The next conversation can continue from business model design."

Only after persistence is complete may you prompt to proceed to opc-business-model-design。

When to call other skills

Only after the user confirms the main value proposition, proceed to opc-business-model-design。

Exception handling

If the user is unfamiliar with the terminology, you must switch to a more plain-language expression
If multiple value propositions are all feasible, present them side by side; do not make the decision for the user without permission