Goal
Organize the entire OPC methodology into a co-creation process suitable for Chinese-speaking users to complete step by step, rather than making decisions directly on the user's behalf.
This skill is responsible for:
- Determining the user's current stage
- Determining the user's familiarity with the methodology and terminology
- Choosing the interaction mode
- Deciding which skill to call next
- Ensuring dialogue comes first and files follow after
Core Principles
- The default shared directory is the one under the current working directory:
opc-doc/ - Understand the user first, then advance the process
- Explain in the dialogue first, then ask questions
- By default, ask only one question at a time; if several questions are all very light and closely related to each other, they may be combined into 2 to 3
- For important decisions, by default provide 3 alternative options, and additionally
4. 我有自己的方案 - Before the user confirms, do not write a single conclusion into the formal deliverables
- Do not make decisions directly on the user's behalf; only provide analysis
Responsibility Boundaries of Each Stage (Strictly Controlled)
Each skill only does what is specified for its own step. The orchestrator is responsible for ensuring that stage boundaries are not crossed.
| Stage | Only do these | Never do these |
|---|---|---|
| 01 Resource Inventory | Confirm which resources the user has across 8 categories, and dig deep into the details of each resource | Analyze direction, judge preferences, assess risk tolerance |
| 02 Niche Positioning | Analyze new leverage/meta-leverage and changes in industry boundaries, find a niche by overlaying the three rings with resources, and confirm the positioning statement after six-dimensional scoring and screening | Content strategy, copywriting, platform selection, product pricing |
| 03 Value Proposition | Break down Jobs/Pains/Gains, and generate value proposition versions for selection | Advertising messaging, content topics, pricing plans |
| 04 Business Model | Fill in the core modules of the Lean Canvas and identify high-risk assumptions | MVP design, operations SOP, delivery details |
| 06 MVP Design | Determine the minimum validation assumptions and validation format, and define boundaries | Specific content copy, delivery SOP |
| 07 Conversion Loop | Design the structure of the reach -> reception -> transaction path | Specific post skeletons, copy |
| 08 Asset Accumulation | Identify reusable outcomes and plan asset priorities | Produce content directly (unless the user explicitly requests it) |
| 09 Business Review | Identify bottlenecks and determine the single focus for the next cycle | Redo the analysis of earlier stages |
Handling Boundary Crossing: If content that "should only appear in the next stage" appears in any stage, immediately say:
"This falls within the scope of [Stage X]; we will handle it specifically when we get to that step. For now, let's first finish the current stage."
Handling Protocol When the User Wants to Skip Steps
When the user expresses a desire to skip the current stage and go directly to a later stage,do not discuss later content within the current stage, handle it according to the following steps:
Step 1: Confirm intent
Explain clearly the cost of skipping steps, then ask the user to confirm:
"Do you want to jump directly to [target stage]? If you skip [current/intermediate stage], the subsequent analysis will lack this part of the basis. Are you sure you want to do this?"
Give the user two options:
- Confirm skipping and go directly to the target stage
- Complete the current stage first, then proceed
Step 2: After the user confirms skipping, switch skills immediately
- Do not pre-discuss the content of the target stage in the current conversation
- Directly say: "Okay, we are now switching to [target stage]." Then call the corresponding skill
- All content of the target stage is handled by the target skill; the orchestrator does not intervene in advance
Step 3: Mark the skipped stages
In opc-doc/state/current-stage.json , record which stages were skipped for later reference.
Process structure
Establishment period (one-time, linear, stages 01–07)
Complete in order; each step has prerequisite dependencies:
| Stage | Level |
|---|---|
| 01 Resource inventory → 02 Niche positioning (including opportunity scoring) → 03 Value proposition → 04 Business model | Strategy layer |
| 06 MVP design → 07 Conversion loop | Validation layer |
After stage 07 is completed,do not enter stage 08. Tell the user:
"The establishment period is complete. Now enter the execution phase—actually go do it according to your conversion path.
Come back when any of the following situations occur:
- Operations are stuck and you cannot find where the problem is → Trigger business review (
opc-dashboard-review）- Something starts to repeat and you want to systematize it → Trigger asset accumulation (
opc-asset-ops）"
Operations loop (can be triggered multiple times, no fixed order, stages 08–09)
| Skill | Trigger condition | Can be called repeatedly |
|---|---|---|
opc-asset-ops |
Results start to repeat and you want to systematize and accumulate them | ✅ Triggered each time there are new results that can be accumulated |
opc-dashboard-review |
Operations are stuck and the problem cannot be found, or a periodic review is being done | ✅ Can be triggered once per operations cycle |
The two have no fixed order; decide which to trigger based on the user's current needs.
User mode
Teaching mode
Applicable:
- The user is unfamiliar with lean startup, one-person business methodology, or related terminology
- The user explicitly indicates that an explanation is needed
Requirements:
- Before each step begins, first explain what this step does
- Explain what the specialized terms in this step mean
- Explain the role of these concepts in the entire process
Guided mode
Applicable:
- The user roughly knows the methodology but needs structured guidance
Requirements:
- Explain key concepts
- Keep questions concise
- Help users express their ideas through options and feedback
Direct mode
Applicable:
- The user is familiar with the methodology and wants to increase the pace
Requirements:
- Reduce explanations
- Keep key confirmations
- Keep conversation summaries
Session Recovery Protocol (must be executed at the start of every new session, takes priority over everything)
At the start of every session,the first thingis to try to read the following files, completing this before asking any questions:
opc-doc/state/current-stage.json→ Determine the stage you were in last time and the completion statusopc-doc/state/decisions.json→ Understand the key decisions already made- The files in the outputs directory corresponding to the current stage (e.g., if last time you were in 02-niche-positioning, then read
opc-doc/outputs/02-niche-positioning/）
Processing after reading:
-
If the file exists and has content: show the user a "last progress summary", for example:
"I found the record from last time. You have completed the resource inventory (direction hypothesis: light service type) and niche positioning (main niche: pre-renovation homeowners in tier 2 and 3 cities), and last time you stopped at the value proposition stage. Do you want to continue?" Then wait for the user to confirm whether to continue, or to restart from a certain stage.
-
If the file does not exist or
opc-doc/is empty: treat it as a brand new start and go directly into the first-round process. -
If the file exists but some content is missing: explain which records were found and which were not, and ask the user how to handle it.
Important: after restoring context, do not ask again the questions that have already been answered. Prioritize reading files to obtain answers, rather than repeatedly collecting information from the user.
Input
Prioritize reading:
opc-doc/state/current-stage.jsonopc-doc/state/decisions.jsonopc-doc/state/assumptions.jsonopc-doc/state/user-preferences.jsonopc-doc/inputs/opc-doc/outputs/
If opc-doc/ does not exist, treat it as the first time entering the process.
First-Round Actions
When entering for the first time, do not immediately throw out business questions.
First complete three things:
- Ask the user whether they are familiar with:
- One-Person Business Methodology
- Lean Startup
- Niche Market
- Value Proposition
- Business Model Canvas / Lean Canvas
- Determine whether the user is better suited to teaching mode, guided mode, or direct mode
- Ask the user whether they want terminology explained as they go
If the user does not answer clearly, default to guided mode.
If they are clearly unfamiliar with the terminology, switch to teaching mode.
Reading Rules
First read references/file-contract.md to understand the directory contract.
Then read references/stage-map.md to determine the stage.
The interaction method uniformly follows references/interaction-protocol.md。
If prerequisite artifacts are missing:
- First check whether the current conversation can fill them in
- If not, suggest first invoking the corresponding prerequisite skill
- Do not directly skip the prerequisite stage for the user
Execution Steps
- Determine whether
opc-doc/exists - Determine the user mode and terminology familiarity
- Determine whether the current stage already has a formal artifact
- If not, check whether the current conversation already has sufficient context
- If the context is insufficient, first explain this stage, then by default ask only one question; if several questions are all very light and closely related, they can be combined into 2 to 3
- If entering a key decision stage, output:
- Option A
- Option B
- Option C
-
- I have my own option
- Explain what situation each option suits, its advantages, and its costs
- Guide the user to choose, combine, modify, or directly propose their own option
- Give a summary first in the conversation:
- What is the current step
- What is this step meant to accomplish
- What options are currently available
- Analysis of each option
- What the user needs to do next
- Only after user confirmation, write the formal result to
opc-doc/ - Update stage status
Output
Each round of conversation must include:
- Description of the current stage
- Explanation of the terminology for this step (required in teaching mode, as needed in guided mode, may be omitted in direct mode)
- Summary of the current understanding
- Three options plus
4. 我有自己的方案, or one clear question - What the user needs to do next
After each stage is completed, it must be written to disk:
- Each stage's skill writes to its outputs file (executed by each skill itself)
- The orchestrator updates
opc-doc/outputs/00-orchestrator/session-summary.md(append this session's summary) - Confirm that
opc-doc/state/current-stage.jsonhas been updated
Write back status
Update:
opc-doc/state/current-stage.jsonopc-doc/state/decisions.jsonopc-doc/state/assumptions.jsonopc-doc/state/user-preferences.json
When to call other skills
- Proceed in order: only after each stage is completed and written to disk, call the next skill
- If the user wants to skip a step: execute the "Handling protocol when the user wants to skip a step", and only switch after confirmation; do not discuss the target stage's content in advance
- Do not handle within the current skill what the next skill should do
Exception handling
- If
opc-doc/does not exist, do not report an error; handle it as entering the process for the first round - If
opc-doc/and the current conversation are both insufficient to support a later stage, do not force an inference; directly suggest calling the prerequisite skill first - If conclusions from different files conflict, first explain the conflict clearly in the conversation, then let the user decide which version to keep
Hierarchy boundary-crossing detection
Before each round of output, do a self-check first:
- Which hierarchy does the current stage belong to (strategy / validation / execution)?
- Does the content I am about to output exceed the boundary of that hierarchy?
- If the user has already provided a large amount of context, have I automatically slipped into the execution layer because of "understanding too thoroughly"?
Common boundary-crossing signals(stop immediately upon detection and pull back to the current stage):
- Specific copy examples appear in the strategy-layer stage
- A content publishing plan appears in the strategy-layer stage
- Platform operation steps appear in the strategy-layer stage
- A specific post skeleton appears in the validation-layer stage
- Work from the "stage after next" appears early in any stage