一键导入
planning-orchestrator
当需要进行产品立项、战略规划或路线图制定时使用。战略规划指挥官,调度产品提案、战略分析(SWOT/Ansoff/波特五力)、OKR、北极星、路线图等子Skill。关键词:产品立项、战略规划、SWOT、OKR、路线图、战略分析、制定目标、产品规划、年度规划。
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
当需要进行产品立项、战略规划或路线图制定时使用。战略规划指挥官,调度产品提案、战略分析(SWOT/Ansoff/波特五力)、OKR、北极星、路线图等子Skill。关键词:产品立项、战略规划、SWOT、OKR、路线图、战略分析、制定目标、产品规划、年度规划。
用 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 | planning-orchestrator |
| description | 当需要进行产品立项、战略规划或路线图制定时使用。战略规划指挥官,调度产品提案、战略分析(SWOT/Ansoff/波特五力)、OKR、北极星、路线图等子Skill。关键词:产品立项、战略规划、SWOT、OKR、路线图、战略分析、制定目标、产品规划、年度规划。 |
| metadata | {"module":"产品商业与战略","sub-module":"战略规划与路线图","type":"orchestrator","version":"10.0","domain_tags":["通用"],"trigger_examples":["帮我做产品立项","制定一下战略规划","设定OKR目标","规划一下产品路线图","做一下SWOT分析"]} |
确保做正确的事,而非正确地做事。
遵循 orchestrator-protocol.md 编排协议。
pipeline: planning-orchestrator
version: 10.0
post_pipeline:
- action: stage-summary
output: output/phase-reports/pm-strategy/planning-orchestrator.md
stages:
- id: phase-1
name: "产品提案"
skills: [product-proposal]
gate:
condition: "提案书人类已签批"
fail_action: "补充数据后重新提交"
- id: phase-2
name: "战略分析"
depends_on: [phase-1]
skills: [strategic-analysis]
gate:
condition: "strategic-analysis.json已生成,战略结论整合完成,人类决策项已确认"
fail_action: "置信度<0.6的项目升级人类校准,战略方向需人类选择"
- id: phase-3
name: "北极星指标"
depends_on: [phase-2]
skills:
- planning-north-star
gate:
condition: "北极星指标人类已选择"
fail_action: "北极星必须人类决策"
- id: phase-3b
name: "OKR设定"
depends_on: [phase-3]
skills:
- planning-okr
gate:
condition: "OKR人类已确认"
fail_action: "OKR达成概率<0.3升级调整"
- id: phase-4
name: "路线图"
depends_on: [phase-3b]
skills:
- planning-roadmap
gate:
condition: "路线图资源人类已审批"
fail_action: "优先级和资源分配必须人类决策"
output/pm-strategy/product-proposal/(product-proposal.md + product-proposal.json)output/pm-strategy/strategic-analysis/(strategic-analysis.json + strategic-analysis.md)本阶段顺序执行两个子Skill:先调用 planning-north-star 生成北极星指标候选,人类选择后,再调用 planning-okr 基于北极星指标生成OKR候选,人类确认。
output/pm-strategy/planning-north-star/(north_star.json)output/pm-strategy/strategic-analysis/strategic-analysis.json 中 swot.strategies)output/pm-strategy/planning-north-star/north_star.json)output/pm-strategy/planning-okr/(okr.json)output/pm-strategy/planning-okr/okr.json)output/pm-strategy/strategic-analysis/strategic-analysis.json 中 swot.strategies)output/pm-strategy/planning-roadmap/(roadmap.json)所有子Skill执行完成后,必须生成阶段总结文档,写入 output/phase-reports/pm-strategy/planning-orchestrator.md,包含以下6项结构(均不可为空):
| 参数 | 值 |
|---|---|
| 子Skill输出路径 | output/pm-strategy/ |
| 总结输出路径 | output/phase-reports/pm-strategy/planning-orchestrator.md |
| 审批记录路径 | output/approvals/{orchestrator-name}/{stage-id}.approval.json |
下游衔接: primary: design-orchestrator(战略规划完成,将战略转化为PRD和设计方案) alternatives: - target: metrics-orchestrator reason: 需先设计度量体系再进入设计 condition: OKR中关键结果缺乏可量化指标支撑时 - target: project-planning-orchestrator reason: 路线图已就绪,直接启动项目规划 condition: 战略规划已充分,需快速进入项目执行时 special_cases: []
| 卡口 | 条件 | 未通过处理 |
|---|---|---|
| 产品提案已审批 | 提案书人类已签批 | 补充数据后重新提交 |
| 战略分析完成 | strategic-analysis.json已生成且非空 | 置信度<0.6的项目升级人类校准,战略方向需人类选择 |
| 目标设定完成 | 北极星指标人类已选择,OKR人类已确认 | 北极星必须人类决策;OKR达成概率<0.3升级调整 |
| 路线图完成 | 路线图资源人类已审批 | 优先级和资源分配必须人类决策 |
| 阶段总结已生成 | output/phase-reports/pm-strategy/planning-orchestrator.md 已生成且6项结构均非空 | 补充缺失结构项后重新生成 |
| 异常类型 | 处理策略 |
|---|---|
| 阶段1某子Skill失败 | 暂停编排,输出失败诊断信息,请求人类介入修复后重试该阶段 |
| strategic-analysis框架选择异常 | 默认选择SWOT框架执行,标注"框架选择降级为SWOT" |
| strategic-analysis某框架分析失败 | 跳过失败框架,基于已完成的框架生成战略结论,标注"XX框架分析缺失" |
| 上游数据缺失 | 标注缺失数据项,使用合理假设填充(标注置信度≤0.3),继续执行并在输出中高亮标注 |
| 关键决策点未获人类确认 | 暂停编排,输出待确认事项清单,等待人类确认后继续 |
| 所有上游数据全部缺失 | 标注"全数据缺失"状态,输出最小化模板(仅含元信息和空结构),整体置信度设为0.3,强制人类确认是否继续。人类确认后基于用户提供信息和AI知识库推断生成,所有推断内容标注confidence≤0.5和needs_human_validation:true |
| 阶段总结生成失败 | 基于已完成的子Skill输出生成部分总结,缺失项标注"数据缺失",不阻塞编排完成 |
| 决策点 | 触发条件 | 决策内容 |
|---|---|---|
| 产品立项审批 | 阶段1 product-proposal 生成产品提案书 | 人类决定是否立项 |
| 战略方向选择 | 阶段2 strategic-analysis 生成战略结论 | 人类选择最终战略方向和增长路径 |
| 目标设定确认 | 阶段3 planning-north-star生成北极星候选后人类选择,planning-okr生成OKR候选后人类确认 | 人类选择北极星指标并确认OKR |
| 路线图优先级 | 阶段4 planning-roadmap 计算RICE评分并排序 | 人类决定最终优先级和资源分配 |