// 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 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.
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-asset-ops |
| description | 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/`. |
帮助用户判断“哪些成果值得沉淀为资产”，而不是替用户一次性搭完整系统。
opc-doc/4. 我有自己的方案注意：资产沉淀阶段是整套方法论中最靠近执行的一步。允许输出具体的模板结构框架，但"填写内容"由用户自己完成，或在用户明确要求后才协助。
教学模式下先解释：
本技能不是建盘期的线性下一步，而是运营循环中的条件触发工具。
触发时机：用户在实际运营中发现某些动作开始重复出现，想把它们系统化，不再每次从零做起。
常见触发信号：
前置条件检查：如果用户还没有实际运营产出（完全没做过），不进入本技能，建议先去执行、再回来。
优先读取：
opc-doc/outputs/06-mvp-design/*opc-doc/outputs/07-conversion-loop/*opc-doc/outputs/08-asset-ops/（历史沉淀记录，本次是否有新增）如果上述文件缺失，判断当前对话中是否已有可复用成果描述。
4. 我有自己的方案对话层必须包含：
4. 我有自己的方案用户明确确认资产沉淀优先方向后，立即使用 Write 工具写入文件。在对话中描述结论不等于落盘。
本技能支持多次触发。每次落盘使用带日期的文件名，不覆盖历史记录。
写入文件（使用当天日期，格式 YYYYMMDD）：
opc-doc/outputs/08-asset-ops/asset-inventory-[YYYYMMDD].md（本次可沉淀成果清单 + 资产类别标注）opc-doc/outputs/08-asset-ops/action-plan-[YYYYMMDD].md（本次确认的优先沉淀方向和下一步动作）更新状态文件：
opc-doc/state/current-stage.json（写入：{"stage": "08-asset-ops", "status": "completed", "next_stage": "execution", "summary": "一句话本次优先沉淀方向"}）opc-doc/state/decisions.json（追加本次资产沉淀优先级决策，注明日期）落盘完成后，在对话中告知用户：
"✅ 本次资产沉淀方案已保存到 opc-doc/。继续去执行——当你运营遇到瓶颈时，可以触发经营复盘（
opc-dashboard-review）。"
opc-dashboard-review