Value Proposition
Objectives
Help users clarify "why should this group of customers buy from you" and provide selectable value proposition solutions.
Core Principles
- Read from and write to the directory under the current working directory by default
- Explain Jobs, Pains, and Gains first in teaching mode
- One customer segment corresponds to one type of value proposition
- Ask only one question at a time by default; if several questions are simple and closely related, they can be combined into 2 to 3 questions
- Provide 3 value proposition directions by default, with an additional option
4. I have my own solution
- Write formal results only after user confirmation
- Do not give direct recommendation conclusions, only conduct solution analysis
- This phase only conducts structured analysis of 'why customers buy from you', and does not enter copy design or content creation
Phase Boundaries
What to do in this phase
- Decompose target users' Jobs / Pains / Gains (structured framework layer)
- Analyze how your products/services correspond to user needs (framework layer)
- Generate 3 versions of value propositions for users to choose from (descriptive language, not promotional copy)
What not to do in this phase (the following belong to subsequent phases, do not enter in advance)
- ❌ Do not write specific advertising copy or promotional scripts (belongs to the asset precipitation phase)
- ❌ Do not design content topics or post structures (belongs to the asset precipitation phase)
- ❌ Do not develop pricing strategies or charging plans (belongs to the business model design phase)
- ❌ Do not design conversion paths or customer acquisition steps (belongs to the conversion closed-loop phase)
Out-of-bound detection: If execution topics such as "how to write a title", "Xiaohongshu copy", "how to persuade users" appear, record them first, then say:
"These execution details are very important, and we will handle them specifically in subsequent phases. Now let's first confirm the logical framework of 'why customers buy from you'."
Mandatory Completion Items for This Phase
- 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
- Key modules of the value proposition canvas are complete
- The user has confirmed the current main value proposition version
Explanation Required in This Phase
Explain the following first in teaching mode:
- Jobs: Tasks that users want to complete
- Pains: The most painful obstacles users encounter when completing tasks
- Gains: Benefits that users ideally want to obtain
- Value proposition: How you plan to help this group of users complete tasks better
Input
Must read first:
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 target segment and positioning have been clarified in the current conversation.
- If not, first recommend calling
Execution Steps
- Explain the objectives and terms of this phase
- Ask only one question at a time by default; if several questions are simple and closely related, they can be combined into 2 to 3 questions, for example:
- What is the most desired result for this type of user?
- What is their biggest pain point right now?
- Why are they dissatisfied with existing solutions?
- 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 reduction type
- Explain the applicable scenarios, advantages and costs of each version
- Add the option
4. I have my own solution
by default
- Allow users to select, combine, modify, or directly propose their own version
- Write formal results only after user confirmation
Output
The conversation layer must include:
- Explanation of this phase
- Summary of current Jobs / Pains / Gains
- 3 value proposition candidates +
4. I have my own solution
- Applicable scenarios, advantages and costs of each solution
- Ask the user to confirm or modify
Persistence Checkpoint (must be completed in this phase, cannot be skipped)
After the user explicitly confirms the main value proposition version, immediately use the Write tool to create the following files on the file system before entering the next phase. Describing conclusions in the conversation does not equal persistence to disk.
Files to write:
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
(correspondence matrix between target customer segments and value propositions)
opc-doc/outputs/03-value-proposition/messaging.md
(confirmed main value proposition statement, framework layer, not advertising copy)
Update status files:
opc-doc/state/current-stage.json
(Write: {"stage": "03-value-proposition", "status": "completed", "next_stage": "04-business-model", "summary": "one-sentence value proposition core"}
)
opc-doc/state/decisions.json
(Append the confirmed value proposition version)
After persistence is completed, inform the user in the conversation:
"✅ Value proposition conclusions have been saved. The next conversation can continue with business model design."
Only after persistence is completed can you prompt to enter opc-business-model-design
.
When to call other skills
Only after the user confirms the main value proposition can you enter
opc-business-model-design
.
Exception Handling
- If the user is not familiar with the terms, you must use more plain language expressions
- If multiple value propositions are feasible, present them side by side, do not make decisions for the user without permission