一键导入
business-orchestrator
当需要设计或评估产品商业模式时使用。商业模式指挥官,调度business-model-canvas/value-fit/pricing/strategy-report。关键词:商业模式、商业画布、定价策略、商业战略报告、怎么赚钱、盈利模式、收费模式、商业评估。
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
当需要设计或评估产品商业模式时使用。商业模式指挥官,调度business-model-canvas/value-fit/pricing/strategy-report。关键词:商业模式、商业画布、定价策略、商业战略报告、怎么赚钱、盈利模式、收费模式、商业评估。
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when managing Sprint cycles or tracking agile execution. Agile execution commander orchestrating agile-sprint-planning, agile-daily-sync, and agile-review sub-skills. agile-review has merged retrospective-auto auto-retrospective capabilities. Keywords: agile execution, Sprint planning, daily standup, Sprint review, agile management, Sprint retrospective, iteration retrospective, agile development, retrospective report, auto-retrospective.
Use when planning a Sprint. Sprint Planning automation, transforming Product Backlog into Sprint Backlog, including Sprint Goal suggestions, Story auto-selection, workload estimation, and capacity matching validation, outputting a complete Sprint plan. Keywords: Sprint planning, Sprint plan, iteration planning, Story selection, capacity matching, scheduling, what to do this iteration.
Use when you need to consolidate competitor tracking data into a complete, deliverable monitoring report. Competitor Dynamic Monitoring Report auto-generation, including competitor dynamics summary, feature change tracking, market strategy changes, threat assessment, and response recommendations. Keywords: competitor monitoring report, competitor dynamics, feature tracking, threat assessment, competitor response, competitor report, what are competitors doing.
Use when you need to track competitor dynamics and develop response strategies. Competitor Dynamic Tracking & Response, monitors competitor feature changes, evaluates dynamic changes in own advantages, generates response strategies, and tracks effectiveness. Keywords: competitor tracking, competitor analysis, competitor monitoring, feature changes, competitive analysis, competitor changes, competitor dynamics, competitor changed, competitor made a move.
Use when you need to diagnose product health. Automated product health diagnosis that collects multi-dimensional data and performs comprehensive scoring, trend prediction, and bottleneck identification, outputting a health report. Keywords: health score, product diagnosis, multi-dimensional scoring, health check, product health, health rating, product checkup, status check.
Use when planning iteration cycles or adjusting product priorities. Iteration decision commander orchestrating iteration-backlog-grooming and iteration-retrospective sub-skills. Keywords: iteration decision, Backlog optimization, priority adjustment, iteration retrospective, iteration planning, requirement restructuring, RICE scoring, iteration management. This orchestrator dispatches 2 sub-skills: Backlog grooming (no cross-module dependencies) and iteration retrospective (depends on pm-08 output).
| name | business-orchestrator |
| description | 当需要设计或评估产品商业模式时使用。商业模式指挥官,调度business-model-canvas/value-fit/pricing/strategy-report。关键词:商业模式、商业画布、定价策略、商业战略报告、怎么赚钱、盈利模式、收费模式、商业评估。 |
| metadata | {"module":"产品商业与战略","sub-module":"商业模式设计","type":"orchestrator","version":"7.1","domain_tags":["电商","SaaS","金融","教育","通用"],"trigger_examples":["帮我设计商业模式","产品怎么赚钱","设计一下定价策略","评估一下商业模式是否可行","做一下商业画布"]} |
商业模式不是设计出来的,是验证出来的。
遵循 orchestrator-protocol.md 编排协议。
pipeline: business-orchestrator
version: 7.1
stages:
- id: phase-1
name: "商业模式画布"
skills: [business-model-canvas]
gate:
condition: "BMC 9格全部填充、假设已标注"
fail_action: "补充缺失要素,无法填充的标注为待验证假设"
- id: phase-2
name: "价值匹配验证"
depends_on: [phase-1]
skills: [business-value-fit]
gate:
condition: "价值主张匹配度≥3.0"
fail_action: "调整价值主张或目标用户,重新验证"
- id: phase-3
name: "定价策略"
depends_on: [phase-1, phase-2]
skills: [business-pricing]
gate:
condition: "3个定价方案已生成"
fail_action: "补充定价方案,确保差异化"
- id: phase-4
name: "商业战略报告"
depends_on: [phase-1, phase-2, phase-3]
skills: [business-strategy-report]
gate:
condition: "报告执行摘要完整,至少2个战略方向"
fail_action: "补充战略方向或标注建议补充战略分析"
post_pipeline:
- action: stage-summary
output: output/phase-reports/pm-strategy/business-orchestrator.md
Skill: business-model-canvas
输入:
product_context: 来自 user-research-user-modeling / opportunity-definition
market_data: 来自 market-competitor-analysis
输出: output/pm-strategy/business-model-canvas/
验证: BMC 9格全部填充、假设已标注
模式: 🤖→👤
Skill: business-value-fit
输入:
bmc_value_proposition: 来自阶段1 output/pm-strategy/business-model-canvas/bmc.json
user_research_data: 来自 user-research-user-modeling / user-research-voice-analysis
输出: output/pm-strategy/business-value-fit/
验证: 价值主张匹配度≥3.0
模式: 🤖
Skill: business-pricing
输入:
bmc_data: 来自阶段1 output/pm-strategy/business-model-canvas/bmc.json
competitor_pricing_data: 来自 market-competitor-analysis → competitor-analysis.json
willingness_to_pay: 用户提供
输出: output/pm-strategy/business-pricing/
验证: 3个定价方案已生成
模式: 🤖→👤
Skill: business-strategy-report
输入:
bmc: 来自阶段1 output/pm-strategy/business-model-canvas/bmc.json
pricing_strategy: 来自阶段3 output/pm-strategy/business-pricing/pricing_analysis.json
product_business_info: 用户提供
optional_inputs: SWOT、OKR、路线图、定位、价值曲线、差异化评估、利益相关者、北极星指标
输出: output/pm-strategy/business-strategy-report/
验证: 报告执行摘要完整,至少2个战略方向
模式: 🤖→👤
所有子Skill执行完成后,必须生成阶段总结文档,写入 output/phase-reports/pm-strategy/business-orchestrator.md,包含以下6项结构(均不可为空):
| 参数 | 值 |
|---|---|
| 子Skill输出路径 | output/pm-strategy/ |
| 总结输出路径 | output/phase-reports/pm-strategy/business-orchestrator.md |
| 审批记录路径 | output/approvals/{orchestrator-name}/{stage-id}.approval.json |
下游衔接: primary: positioning-orchestrator(商业模式设计完成,确定差异化定位策略) alternatives: - target: planning-orchestrator reason: 定位已明确,直接进入战略规划 condition: 产品定位已在商业模式设计中确定时 - target: design-orchestrator reason: 商业模式和定位均已确定,直接进入设计 condition: 商业模式与定位均已完成,需快速进入产品构建时 special_cases: []
| 卡口 | 条件 | 未通过处理 |
|---|---|---|
| BMC生成完成 | business-model-canvas输出文件已生成且非空 | 补充缺失要素,无法填充的标注为待验证假设 |
| 定价方案完成 | pricing输出文件已生成且非空 | 补充缺失方案,确保差异化定位 |
| 商业战略报告完成 | strategy-report输出文件已生成且非空 | 补充战略方向或标注"建议补充战略分析" |
| 阶段总结已生成 | output/phase-reports/pm-strategy/business-orchestrator.md 已生成且6项结构均非空 | 补充缺失结构项后重新生成 |
| 异常类型 | 处理策略 |
|---|---|
| 阶段1某子Skill失败 | 暂停编排,输出失败诊断信息,请求人类介入修复后重试该阶段 |
| 上游数据缺失 | 标注缺失数据项,使用合理假设填充(标注置信度≤0.3),继续执行并在输出中高亮标注 |
| 关键决策点未获人类确认 | 暂停编排,输出待确认事项清单,等待人类确认后继续 |
| 所有上游数据全部缺失 | 标注"全数据缺失"状态,输出最小化模板(仅含元信息和空结构),整体置信度设为0.3,强制人类确认是否继续。人类确认后基于用户提供信息和AI知识库推断生成,所有推断内容标注confidence≤0.5和needs_human_validation:true |
| 阶段总结生成失败 | 基于已完成的子Skill输出生成部分总结,缺失项标注"数据缺失",不阻塞编排完成 |
| 决策点 | 触发条件 | 决策内容 |
|---|---|---|
| 收入模型选择 | 阶段1 business-model-canvas 生成多个收入模式选项 | 人类选择最终收入模式方案 |
| 定价数字拍板 | 阶段3 business-pricing 提供定价分析和方案 | 人类决定具体定价数字和套餐结构 |
| 商业战略方向确认 | 阶段4 business-strategy-report 推荐战略方向 | 人类确认最终战略选择 |