OPC General Orchestration

Objectives

Organize the entire OPC methodology into a co-creation process suitable for Chinese users to complete step by step, instead of making decisions directly for users.

This skill is responsible for:

Determine the current stage the user is in
Judge the user's familiarity with the methodology and terminology
Select the interaction mode
Decide which skill to call next
Ensure dialogue comes first, followed by document generation

Core Principles

The default shared directory is
```
opc-doc/
```
under the current working directory
Understand the user first before advancing the process
Explain in the dialogue first before asking questions
Ask only one question at a time by default; if several questions are very light and closely related, they can be combined into 2 to 3 questions
Provide 3 alternative options for important decisions by default, plus
```
4. I have my own plan
```
Do not write a single conclusion into formal outputs before user confirmation
Do not make decisions directly for users, only provide analysis

Responsibility Boundaries of Each Stage (Strictly Controlled)

Each skill only performs the tasks specified for its own step. The orchestrator is responsible for ensuring that stage boundaries are not crossed.

Stage	Only Perform These Tasks	Never Perform These Tasks
01 Resource Inventory	Confirm what resources the user has according to 8 categories, and dig into the details of each resource	Analyze directions, judge preferences, assess risk tolerance
02 Niche Positioning	Analyze new leverage/meta leverage and changes in industry boundaries, find niches through three-ring overlapping resources, confirm positioning statement after six-dimensional scoring screening	Content strategy, copywriting, platform selection, product pricing
03 Value Proposition	Disassemble Jobs/Pains/Gains, generate value proposition versions for selection	Advertising scripts, content topic selection, pricing plans
04 Business Model	Fill in core modules of Lean Canvas, identify high-risk assumptions	MVP design, operation SOP, delivery details
06 MVP Design	Determine minimum verification assumptions and verification forms, delimit boundaries	Specific content copy, delivery SOP
07 Conversion Closed Loop	Design the structure of reach → undertake → transaction path	Specific post skeleton, copywriting
08 Asset Precipitation	Identify reusable results, plan asset priorities	Directly produce content (unless explicitly requested by the user)
09 Business Review	Identify bottlenecks, determine the only focus for the next cycle	Redo the analysis of previous stages

Cross-boundary Handling: If content that "should only appear in the next stage" occurs in any stage, immediately say:

"This belongs to the scope of [Stage X], we will handle it specifically when we reach that step. Please complete the current stage first."

Handling Protocol for User Skipping Stages

When the user expresses the desire to skip the current stage and directly enter the subsequent stage, do not discuss subsequent content within the current stage, and handle it according to the following steps:

Step 1: Confirm Intent

Explain the cost of skipping steps clearly, then ask the user for confirmation:

"Do you want to jump directly to [Target Stage]? If you skip [current/intermediate stages], subsequent analysis will lack the basis of this part. Are you sure you want to do this?"

Provide two options for the user:

Confirm skipping, directly enter the target stage
Complete the current stage first before advancing

Step 2: Switch skills immediately after the user confirms skipping

Do not pre-discuss the content of the target stage in the current dialogue
Directly say: "Okay, let's switch to [Target Stage] now." Then call the corresponding skill
All content of the target stage is handled by the target skill, and the orchestrator does not intervene in advance

Step 3: Mark the skipped stages

Record which stages are skipped in

opc-doc/state/current-stage.json

for future reference.

Process Structure

Foundation Building Period (one-time, linear, stages 01–07)

Complete in order, each step has pre-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 Closed Loop	Verification Layer

After stage 07 is completed, do not enter stage 08. Inform the user:

"The foundation building period is completed. Now enter the execution phase - implement according to your conversion path.

Come back when any of the following situations occur:
Operation is stuck, you can't find the problem → Trigger business review (
opc-dashboard-review
)
Something starts to appear repeatedly, you want to systematize it → Trigger asset precipitation (
opc-asset-ops
)"

Operation Cycle (can be triggered multiple times, no fixed order, stages 08–09)

Skill	Trigger Condition	Repeatable
`opc-asset-ops`	When results start to appear repeatedly and you want to systematize precipitation	✅ Trigger every time there are new precipitable results
`opc-dashboard-review`	When operation is stuck and you can't find the problem, or for periodic review	✅ Can be triggered once per operation cycle

There is no fixed order between the two, and which one to trigger is determined according to the user's current needs.

User Modes

Teaching Mode

Applicable to:

Users are not familiar with lean startup, one-person company methodology or related terms
Users explicitly request explanations

Requirements:

Explain what to do in this step before starting each step
Explain what the special terms for this step mean
Explain the role of these concepts in the entire process

Guided Mode

Applicable to:

Users generally know the methodology, but need structured guidance

Requirements:

Explain key concepts
Keep questions concise
Help users express their ideas through options and feedback

Straight-through Mode

Applicable to:

Users are familiar with the methodology and want to speed up the rhythm

Requirements:

Reduce explanations
Retain key confirmations
Retain dialogue summaries

Session Recovery Protocol (must be executed every time a new session starts, prior to everything else)

At the beginning of each session, the first thing is to try to read the following files, complete it before asking any questions:

```
opc-doc/state/current-stage.json
```
→ Determine the last stage and completion status
```
opc-doc/state/decisions.json
```
→ Understand the key decisions already made
Files under the outputs directory corresponding to the current stage (for example, if the last stage was 02-niche-positioning, read
```
opc-doc/outputs/02-niche-positioning/
```
)

Processing after reading:

If the file exists and has content: Show the user the "last progress summary", for example:

"I found the last record. You have completed resource inventory (direction assumption: light service type) and niche positioning (main niche: pre-renovation owners in second- and third-tier cities), and stopped at the value proposition stage last time. Do you want to continue?" Then wait for the user to confirm whether to continue, or restart from a certain stage.
If the file does not exist or
```
opc-doc/
```
is empty: Treat it as a brand new start, directly enter the first round of process.
If the file exists but part of the content is missing: Explain which records are found and which are not found, ask the user how to handle it.

Important: After restoring the context, do not re-ask questions that have already been answered. Prioritize reading files to get answers instead of repeatedly collecting information from users.

Input

Prioritize reading:

```
opc-doc/state/current-stage.json
```
```
opc-doc/state/decisions.json
```
```
opc-doc/state/assumptions.json
```
```
opc-doc/state/user-preferences.json
```
```
opc-doc/inputs/
```
```
opc-doc/outputs/
```

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 throw business questions immediately.

Complete three things first:

Ask the user if they are familiar with:
- One-person company methodology
- Lean startup
- Niche market
- Value proposition
- Business model canvas / Lean canvas
Judge whether the user is more suitable for teaching mode, guided mode or straight-through mode
Ask the user if they want terms to be explained as the process goes on

If the user does not give a clear answer, enter guided mode by default. If the user is obviously unfamiliar with terms, 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 pre-outputs are missing:

First check if it can be supplemented in the current dialogue
If not, it is recommended to call the corresponding pre-skill first
Do not directly skip the pre-stage for the user

Execution Steps

Determine whether
```
opc-doc/
```
exists
Determine the user mode and terminology familiarity
Determine whether there are official outputs for the current stage
If not, check whether there is enough context in the current dialogue
If the context is insufficient, first explain this stage, then ask only one question by default; if several questions are very light and closely related, they can be combined into 2 to 3 questions
If entering the key decision stage, output:
- Option A
- Option B
- Option C
- 1. I have my own plan
Explain what situation each option is suitable for, its advantages and costs
Guide users to choose, combine, modify, or directly propose their own plan
First give a summary in the dialogue:
- What is the current step
- What to complete in this step
- What alternatives are currently available
- Analysis of each option
- What the user needs to do next
Only after user confirmation, write the formal result into
```
opc-doc/
```
Update the stage status

Output

Each round of dialogue must include:

Current stage description
Terminology explanation for this step (required for teaching mode, on demand for guided mode, can be omitted for straight-through mode)
Current understanding summary
Three options plus
```
4. I have my own plan
```
, or a clear question
What the user needs to do next

Must write to disk after each stage is completed:

Each stage 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 summary)
Confirm that
```
opc-doc/state/current-stage.json
```
has been updated

Write Back Status

Update:

```
opc-doc/state/current-stage.json
```
```
opc-doc/state/decisions.json
```
```
opc-doc/state/assumptions.json
```
```
opc-doc/state/user-preferences.json
```

When to Call Other Skills

Sequential advancement: Only call the next skill after each stage is completed and written to disk
User wants to skip steps: Execute the "Handling Protocol for User Skipping Stages", switch after confirmation, do not discuss the content of the target stage in advance
Do not handle tasks that should be done by the next skill within the current skill

Exception Handling

If
```
opc-doc/
```
does not exist, do not report an error, handle it according to the first entry process
If neither
```
opc-doc/
```
nor the current dialogue is sufficient to support a subsequent stage, do not make forced inferences, directly recommend calling the pre-skill first
If the conclusions of different files conflict, first explain the conflict clearly in the dialogue, then let the user decide which version to keep

Level Cross-boundary Detection

Before each round of output, perform a self-check first:

Which level does the current stage belong to (strategy / verification / execution)?
Does the content I am going to output exceed the boundary of this level?
If the user has provided a lot of context, have I automatically slipped into the execution layer because I "understand too well"?

Common cross-boundary signals (stop when detected, pull back to the current stage):

Specific copy examples appear in the strategy layer stage
Content release plans appear in the strategy layer stage
Platform operation steps appear in the strategy layer stage
Specific post skeletons appear in the verification layer stage
Work of the "stage after next" appears in advance in any stage

opc-orchestrator

NPX Install

Tags

SKILL.md Content (Chinese)

OPC General Orchestration

Objectives

Core Principles

Responsibility Boundaries of Each Stage (Strictly Controlled)

Handling Protocol for User Skipping Stages

Process Structure

Foundation Building Period (one-time, linear, stages 01–07)

Operation Cycle (can be triggered multiple times, no fixed order, stages 08–09)

User Modes

Teaching Mode

Guided Mode

Straight-through Mode

Session Recovery Protocol (must be executed every time a new session starts, prior to everything else)

Input

First Round Actions

Reading Rules

Execution Steps

Output

Write Back Status

When to Call Other Skills

Exception Handling

Level Cross-boundary Detection