// Design a conversion loop for a one-person company from reach to lead capture to purchase. Use when Codex needs to explain conversion concepts when needed, verify MVP prerequisites, ask one question at a time, present multiple conversion-path options, and write user-confirmed outputs into `opc-doc/`.
Design a viable business model for a one-person company using Lean Canvas and a simplified Business Model Canvas. Use when Codex needs to explain the business-model concepts when needed, verify niche and value-proposition prerequisites, ask one question at a time, present multiple model choices, and write user-confirmed outputs into `opc-doc/`.
Define the smallest viable experiment and MVP for a selected one-person company opportunity. Use when Codex needs to explain what MVP means when needed, verify prerequisites, ask one question at a time, present multiple MVP options, and write user-confirmed outputs into `opc-doc/`.
Inventory all founder resources across 8 categories for a one-person company. Use when Codex needs to systematically confirm what resources the founder has — experience, network, skills, relationships, channels, assets, time/money constraints, hard limits — by first doing a broad scan of each category, then drilling into specifics (distribution, usable portions, how to use, cost of use), and producing a confirmed detailed resource inventory written to `opc-doc/`. Does NOT analyze directions, preferences, suitability, or risk tolerance — those belong to downstream skills.
Turn repeatable outputs of a one-person company into compounding assets. Use when Codex needs to explain asset-compounding concepts when needed, verify prerequisite outputs, ask one question at a time, present multiple assetization priorities, and write user-confirmed outputs into `opc-doc/`.
Review the operating health of a one-person company using lightweight metrics, bottleneck analysis, and stop-loss logic. Use when Codex needs to explain review concepts when needed, verify available outputs, ask one question at a time, present multiple bottleneck hypotheses, and write user-confirmed outputs into `opc-doc/`.
Find and position a viable niche market for a one-person company by combining market mapping and customer segmentation. Use when Codex needs to explain niche concepts when needed, check founder-resource prerequisites, ask one question at a time, generate multiple niche options, and write user-confirmed positioning outputs into `opc-doc/`.
| name | opc-conversion-loop |
| description | Design a conversion loop for a one-person company from reach to lead capture to purchase. Use when Codex needs to explain conversion concepts when needed, verify MVP prerequisites, ask one question at a time, present multiple conversion-path options, and write user-confirmed outputs into `opc-doc/`. |
帮助用户设计“怎么触达、怎么承接、怎么成交”的路径，而不是直接替用户定一条路线。
opc-doc/4. 我有自己的方案越界检测：如果出现"第一篇帖子怎么写""具体怎么说服用户""封面怎么设计"等话题，先记录，再说：
"这些属于内容资产阶段的工作。现在先把转化路径的结构确认好，后面的内容才有方向。"
教学模式下先解释：
优先读取：
opc-doc/outputs/06-mvp-design/*如果没有明确 MVP，先建议回到 opc-mvp-designer。
4. 我有自己的方案对话层必须包含：
4. 我有自己的方案用户明确确认转化路径后，立即使用 Write 工具在文件系统上创建以下文件，然后才能进入下一阶段。在对话中描述结论不等于落盘。
写入文件：
opc-doc/outputs/07-conversion-loop/channel-strategy.md（目标渠道选择及依据）opc-doc/outputs/07-conversion-loop/content-plan.md（内容触达方式类别，非具体选题）opc-doc/outputs/07-conversion-loop/conversion-path.md（完整转化路径：触达 → 承接 → 成交）更新状态文件：
opc-doc/state/current-stage.json（写入：{"stage": "07-conversion-loop", "status": "completed", "next_stage": "08-asset-ops", "summary": "一句话主转化路径"}）opc-doc/state/decisions.json（追加转化路径确认）落盘完成后，在对话中告知用户：
"✅ 转化闭环方案已保存。下次对话可以从资产沉淀继续。"
只有落盘完成后，才可以提示进入 opc-asset-ops 或 opc-dashboard-review。
只有在用户确认转化路径后，才进入 opc-asset-ops 或 opc-dashboard-review。