菜单
当需要确定产品定位或评估差异化策略时使用。产品定位指挥官，调度positioning-strategy。关键词：产品定位、差异化、价值曲线、竞争策略、品牌定位、市场定位、竞争优势。本编排器为透传编排器，仅调度1个子Skill(positioning-strategy)，上层编排器也可直接调用positioning-strategy。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | positioning-orchestrator |
| description | 当需要确定产品定位或评估差异化策略时使用。产品定位指挥官，调度positioning-strategy。关键词：产品定位、差异化、价值曲线、竞争策略、品牌定位、市场定位、竞争优势。本编排器为透传编排器，仅调度1个子Skill(positioning-strategy)，上层编排器也可直接调用positioning-strategy。 |
| metadata | {"module":"产品商业与战略","sub-module":"产品定位与差异化","type":"orchestrator","version":"8.0","domain_tags":["通用"],"trigger_examples":["帮我确定产品定位","分析一下差异化优势","写一个定位陈述","评估一下竞争策略"]} |
定位的本质是选择不为谁服务。
本编排器当前 Pipeline 仅包含 1 个子 Skill（positioning-strategy），属于合并简化后的退化编排器。保留本编排器的理由：
若未来该子模块需要扩展为多阶段 Pipeline，本编排器可直接增加阶段，无需修改上层编排器的调用方式。
遵循 orchestrator-protocol.md 编排协议。
本编排器为透传编排器，职责是提供统一入口、阶段总结和异常处理。上层编排器（如product-launch-orchestrator）可直接调用positioning-strategy子Skill，无需经过本编排器。
pipeline: positioning-orchestrator
version: 8.0
post_pipeline:
- action: stage-summary
output: output/phase-reports/pm-strategy/positioning-orchestrator.md
stages:
- id: phase-1
name: "定位策略"
skills: [positioning-strategy]
gate:
condition: "positioning-strategy输出文件已生成"
fail_action: "按子Skill失败原因处理，必要时升级人类"
positioning-strategyvalue_fit: 价值主张匹配结果（来自 output/pm-strategy/business-value-fit/evaluation_report.json）competitor_analysis: 竞品分析数据（来自 market-competitor-analysis → competitor-analysis.json）user_insight: 用户洞察（来自 user-research-user-modeling）bmc: 价值主张（来自 output/pm-strategy/business-model-canvas/bmc.json，可选）capability_assessment: 自身能力评估（可选，用户提供）output/pm-strategy/positioning-strategy/positioning-strategy.json + output/pm-strategy/positioning-strategy/positioning-strategy.md所有子Skill执行完成后，必须生成阶段总结文档，写入 output/phase-reports/pm-strategy/positioning-orchestrator.md，包含以下6项结构（均不可为空）：
| 参数 | 值 |
|---|---|
| 子Skill输出路径 | output/pm-strategy/ |
| 总结输出路径 | output/phase-reports/pm-strategy/positioning-orchestrator.md |
| 审批记录路径 | output/approvals/{orchestrator-name}/{stage-id}.approval.json |
下游衔接: primary: planning-orchestrator（定位策略完成，制定OKR和路线图） alternatives: - target: business-orchestrator reason: 定位结果影响商业模式，需回溯调整 condition: 定位策略与现有商业模式不一致时 - target: design-orchestrator reason: 定位已清晰且规划已完成，直接进入设计 condition: OKR和路线图已在前序阶段完成时 special_cases: []
| 卡口 | 条件 | 未通过处理 |
|---|---|---|
| 输出文件已生成 | positioning-strategy.json 已生成 | 按子Skill失败原因处理，必要时升级人类 |
| 阶段总结已生成 | output/phase-reports/pm-strategy/positioning-orchestrator.md 已生成且6项结构均非空 | 补充缺失结构项后重新生成 |
| 决策点 | 触发条件 | 决策内容 |
|---|---|---|
| 定位陈述最终选择 | positioning-strategy 生成候选定位陈述 | 人类选择最终定位陈述 |
| 排他决策 | positioning-strategy 提供排他建议 | 人类决定不为哪些用户服务 |
| 异常类型 | 处理策略 |
|---|---|
| 子Skill执行失败 | 暂停编排，输出失败诊断信息，请求人类介入修复后重试 |
| 上游数据缺失 | 标注缺失数据项，使用合理假设填充（标注置信度≤0.3），继续执行并在输出中高亮标注 |
| 关键决策点未获人类确认 | 暂停编排，输出待确认事项清单，等待人类确认后继续 |
| 阶段总结生成失败 | 基于已完成的子Skill输出生成部分总结，缺失项标注"数据缺失"，不阻塞编排完成 |
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).