Conversion Loop
Objective
Help users design the path of "how to reach, how to capture leads, how to close deals", instead of directly deciding a route for users.
Core Principles
- Read and write from the directory under the current working directory by default
- Explain "conversion loop" first in teaching mode
- 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 optional conversion paths by default, with an additional option
- Write the formal result only after user confirmation
- Do not give direct recommendation conclusions, only conduct solution analysis
- This phase only focuses on the path structure of "reach → lead capture → deal closing", and does not involve specific content or copywriting creation
Phase Boundaries
What to do in this step
- Confirm target channels (where to reach users)
- Confirm lead capture methods (how to capture incoming leads)
- Confirm the first deal closing action (how to complete the first order)
- Confirm the complete conversion path structure
What not to do in this step (the following belong to subsequent phases, do not proceed in advance)
- ❌ Do not write specific content topics, post structures or copies (belongs to opc-asset-ops)
- ❌ Do not design specific product packaging scripts (belongs to opc-asset-ops)
- ❌ Do not make operation SOPs or delivery details (belongs to opc-asset-ops)
Boundary detection: If topics such as "how to write the first post", "how to persuade users specifically", "how to design the cover" appear, record them first, then say:
"These belong to the content asset phase. Let's confirm the structure of the conversion path first, so that the subsequent content will have a clear direction."
Mandatory deliverables for this step
- Clarify target channels
- Clarify lead capture actions
- Clarify low-friction deal closing actions
- Clarify the complete conversion path
Priority confirmation order
- Channels where target users appear most frequently
- How to capture leads
- How to complete the first deal
- How to close the loop of the entire conversion path
Completion criteria
- A clear conversion path plan has been formed
- The user has confirmed the current main path
What to explain in this step
Explain first in teaching mode:
- Conversion loop is the complete path from being seen to final deal closing
- The key is not only traffic, but also whether there are lead capture and deal closing actions
- This step will determine how you get your first batch of users
Input
Read first by priority:
opc-doc/outputs/06-mvp-design/*
If there is no clear MVP, it is recommended to return to
first.
Execution steps
- Explain the goal of this step
- 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:
- Where do your target users appear most often?
- Are you better at content, private chat or direct sales?
- Are you willing to sell low-price entry products first or directly sell high-ticket products?
- Give immediate feedback after each round of answers
- Generate 3 conversion paths, for example:
- Content -> Private message -> Consultation -> Deal closing
- Content -> Form -> Diagnosis -> Deal closing
- Low-price product -> Upgraded service
- Explain the applicable scenarios, advantages and costs of each path
- Add option 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 current understanding of channels and deal closing
- 3 conversion path plans +
- Applicable scenarios, advantages and costs of each plan
- Ask the user to confirm or modify
Persistence checkpoint (must be completed in this phase, cannot be skipped)
After the user explicitly confirms the conversion path, immediately use the Write tool to create the following files in the file system before proceeding to the next phase. Describing the conclusion in the conversation does not equal to persistence to disk.
Files to write:
opc-doc/outputs/07-conversion-loop/channel-strategy.md
(Target channel selection and basis)
opc-doc/outputs/07-conversion-loop/content-plan.md
(Content reach method categories, not specific topics)
opc-doc/outputs/07-conversion-loop/conversion-path.md
(Complete conversion path: reach → lead capture → deal closing)
Update status files:
opc-doc/state/current-stage.json
(Write: {"stage": "07-conversion-loop", "status": "completed", "next_stage": "08-asset-ops", "summary": "One-sentence main conversion path"}
)
opc-doc/state/decisions.json
(Append conversion path confirmation)
After the persistence is completed, inform the user in the conversation:
"✅ The conversion loop plan has been saved. The next conversation can continue from asset precipitation."
Only after the persistence is completed can you prompt to enter or .
When to call other skills
Only after the user confirms the conversion path, enter
or
.
Exception handling
- If there are too many channels, help users narrow down to 1 to 2 channels
- If there is no lead capture action, it is not a closed loop