// 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/`.
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/`.
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/`.
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/`.
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-mvp-designer |
| description | 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/`. |
帮助用户确定“最先验证什么、用什么最小形式去验证”，而不是替用户直接定一个产品。
opc-doc/4. 我有自己的方案越界检测：如果出现"第一篇帖子写什么""具体怎么做这次验证""文案怎么写"等执行话题，先记录，再说：
"这些执行细节会在转化闭环和资产沉淀阶段处理。现在先把验证路径的框架确认好。"
教学模式下先解释：
优先读取：
opc-doc/outputs/04-business-model/risky-assumptions.md如果依赖不完整，先建议回到 opc-business-model-design。
4. 我有自己的方案对话层必须包含：
4. 我有自己的方案用户明确确认 MVP 方案后，立即使用 Write 工具在文件系统上创建以下文件，然后才能进入下一阶段。在对话中描述结论不等于落盘。
写入文件：
opc-doc/outputs/06-mvp-design/mvp-spec.md（验证假设 + 最小验证形式 + MVP 边界）opc-doc/outputs/06-mvp-design/experiment-plan.md（成功标准 + 验证周期）opc-doc/outputs/06-mvp-design/human-ai-split.md（人工 vs AI 分工说明）更新状态文件：
opc-doc/state/current-stage.json（写入：{"stage": "06-mvp-design", "status": "completed", "next_stage": "07-conversion-loop", "summary": "一句话 MVP 核心"}）opc-doc/state/assumptions.json（更新已验证/待验证假设状态）落盘完成后，在对话中告知用户：
"✅ MVP 方案已保存。下次对话可以从转化闭环继续。"
只有落盘完成后，才可以提示进入 opc-conversion-loop。
只有在用户确认 MVP 方案后，才进入 opc-conversion-loop。