ワンクリックで
ideation-orchestrator
当需要发散创意或构思解决方案时使用。创意发散与方案构思子模块指挥官,调度子Skill:ideation-workshop。关键词:创意发散、HMW、SCAMPER、方案构思、产品创意、思维逆转、方案收敛、头脑风暴、创新方案、创意工作坊。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
当需要发散创意或构思解决方案时使用。创意发散与方案构思子模块指挥官,调度子Skill:ideation-workshop。关键词:创意发散、HMW、SCAMPER、方案构思、产品创意、思维逆转、方案收敛、头脑风暴、创新方案、创意工作坊。
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 | ideation-orchestrator |
| description | 当需要发散创意或构思解决方案时使用。创意发散与方案构思子模块指挥官,调度子Skill:ideation-workshop。关键词:创意发散、HMW、SCAMPER、方案构思、产品创意、思维逆转、方案收敛、头脑风暴、创新方案、创意工作坊。 |
| metadata | {"module":"产品构思与设计","sub-module":"创意发散与方案构思","type":"orchestrator","version":"7.0","domain_tags":["通用"],"trigger_examples":["帮我发散一下创意","构思一下解决方案","用SCAMPER方法创新","头脑风暴一下"]} |
| 异常类型 | 处理策略 |
|---|---|
| 子Skill输出文件缺失 | 阻塞当前阶段,提示人类补充上游输入或提供替代数据 |
| HMW维度覆盖不全 | 针对缺失维度补充生成,最多重试2次,仍不全则标注"维度覆盖不完整" |
| SCAMPER方案数量不足 | 针对稀缺维度补充生成,仍不足则降低方案数量阈值并标注 |
| 收敛阶段对比矩阵维度缺失 | 补充缺失维度评分,无法评分则标注"数据不足" |
| 人类决策超时未响应 | 暂停编排流程,保留当前状态,等待人类决策后继续 |
| 上下文接近上限 | 优先保留当前阶段内容,将已完成阶段的输出摘要为关键结论写入文件 |
| 阶段总结生成失败 | 基于已完成的子Skill输出生成部分总结,缺失项标注"数据缺失",不阻塞编排完成 |
遵循 orchestrator-protocol.md 编排协议。
pipeline: ideation-orchestrator
version: 7.0
post_pipeline:
- action: stage-summary
output: output/phase-reports/pm-design/ideation-orchestrator.md
stages:
- id: phase-1
name: "创意工作坊"
depends_on: []
skills: [ideation-workshop]
gate:
condition: "HMW 6维度覆盖、SCAMPER 7维度覆盖且至少10个方案、反转思维设计约束已生成、Top5方案已深化且对比矩阵6维度完整"
fail_action: "针对不达标项补充生成或重新深化"
Skill: ideation-workshop
输入:
problem_statement: 用户提供(或上游产出)
user_research_data: 用户提供(或上游产出)
current_solution: 可选
competitor_solutions: 可选
product_context: 可选
输出: output/pm-design/ideation-workshop/ideation-workshop.json + ideation-workshop.md
验证: HMW通过质量检查且6个维度都已覆盖;SCAMPER至少10个候选方案且7个维度都已覆盖;反转思维设计约束已生成且失败路径覆盖5个维度;Top5方案已深化且对比矩阵6个维度完整
模式: 🤖→👤
所有子Skill执行完成后,必须生成阶段总结文档,写入 output/phase-reports/pm-design/ideation-orchestrator.md,包含以下6项结构(均不可为空):
| 参数 | 值 |
|---|---|
| 子Skill输出路径 | output/pm-design/ideation-workshop/ |
| 总结输出路径 | output/phase-reports/pm-design/ideation-orchestrator.md |
| 审批记录路径 | output/approvals/{orchestrator-name}/{stage-id}.approval.json |
下游衔接: primary: design-orchestrator(创意发散完成,将创意方案转化为PRD) alternatives: - target: validation-orchestrator reason: 创意方案存在高风险假设,需先验证 condition: 创意方案中关键假设风险等级≥高时 - target: opportunity-orchestrator reason: 创意方向不明确,需回溯到机会定义 condition: 创意收敛后仍无法形成明确产品方向时 special_cases: []
| 卡口 | 条件 | 未通过处理 |
|---|---|---|
| 创意工作坊完成 | ideation-workshop输出文件已生成且非空 | 针对不达标项补充生成或重新深化 |
| 阶段总结已生成 | output/phase-reports/pm-design/ideation-orchestrator.md 已生成且6项结构均非空 | 补充缺失结构项后重新生成 |
| 决策点 | 触发条件 | 决策内容 |
|---|---|---|
| 方案最终选择 | 创意工作坊收敛完成,对比矩阵已生成 | 人类做最终方案选择,可接受AI推荐、调整优先级、组合方案或否决 |