skills/opc-business-model-design/SKILL.md
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/`.
npx skillsauth add easychen/opc-methodology opc-business-model-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
帮助用户把“这个生意如何成立”拆清楚,而不是直接替用户填完一张画布。
opc-doc/4. 我有自己的方案越界检测:如果出现"我先做哪个功能""怎么开始第一单""怎么发内容"等话题,先记录,再说:
"这属于后续 MVP 或执行阶段的范围。我们先把商业模式的假设确认清楚,再推进。"
优先完成 Lean Canvas 的核心模块:
在此基础上,再用 BMC Lite 做轻量校验。
教学模式下先解释:
必须优先读取:
opc-doc/outputs/02-niche-positioning/*opc-doc/outputs/03-value-proposition/*如果前置结果不足,先建议回到对应前置 skill。
4. 我有自己的方案对话层必须包含:
4. 我有自己的方案用户明确确认核心商模方向后,立即使用 Write 工具在文件系统上创建以下文件,然后才能进入下一阶段。在对话中描述结论不等于落盘。
写入文件:
opc-doc/outputs/04-business-model/lean-canvas.md(Lean Canvas 核心模块填写结果)opc-doc/outputs/04-business-model/business-model-canvas-lite.md(BMC Lite 轻量校验)opc-doc/outputs/04-business-model/pricing-notes.md(收费方式假设)opc-doc/outputs/04-business-model/risky-assumptions.md(高风险假设清单,供 MVP 阶段优先验证)更新状态文件:
opc-doc/state/current-stage.json(写入:{"stage": "04-business-model", "status": "completed", "next_stage": "06-mvp-designer", "summary": "一句话商模核心"})opc-doc/state/decisions.json(追加核心商模决策)opc-doc/state/assumptions.json(写入高风险假设列表)落盘完成后,在对话中告知用户:
"✅ 商业模式结论已保存。下次对话可以从 MVP 设计继续。"
只有落盘完成后,才可以提示进入 opc-mvp-designer。
只有在用户确认核心商模后,才进入 opc-mvp-designer。
development
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.
development
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/`.
development
Design value propositions for candidate customer segments and help the user choose the strongest one. Use when Codex needs to explain jobs, pains, and gains when needed, check niche-positioning prerequisites, ask one question at a time, present multiple value-proposition options, and write user-confirmed outputs into `opc-doc/`.
development
Orchestrate the full one-person company workflow across all OPC skills. Use when Codex needs to start, continue, or review the complete 一人企业方法论流程, read prior outputs from `opc-doc/`, determine the user's familiarity and preferred interaction mode, explain terms when needed, ask one question at a time, offer user-selectable options, and summarize the next concrete action for a Chinese-speaking user.