agentsclimarketplace

Ideation orchestrator

Skill LuckyOneTwoThree/pm-skill/pm-03-design/orchestrators/ideation-orchestrator

当需要发散创意或构思解决方案时使用。创意发散与方案构思子模块指挥官,调度子Skill:ideation-workshop。关键词:创意发散、HMW、SCAMPER、方案构思、产品创意、思维逆转、方案收敛、头脑风暴、创新方案、创意工作坊。From its SKILL.md

Install
npx -y skills add LuckyOneTwoThree/pm-skill --skill ideation-orchestrator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.9 KB, ~1.9k tokens by cl100k_base, as published. Nobody here has run it

创意发散与方案构思指挥官

核心原则

  1. 创意质量与数量正相关——早期判断是创意的敌人,先发散再收敛
  2. 约束是创意的护栏不是枷锁——思维逆转提供的约束确保方案不踩坑,而非限制想象力
  3. 收敛必须有结构化依据——对比矩阵和假设验证为方案选择提供客观支撑,直觉决策是最后手段

异常处理

异常类型处理策略
子Skill输出文件缺失阻塞当前阶段,提示人类补充上游输入或提供替代数据
HMW维度覆盖不全针对缺失维度补充生成,最多重试2次,仍不全则标注"维度覆盖不完整"
SCAMPER方案数量不足针对稀缺维度补充生成,仍不足则降低方案数量阈值并标注
收敛阶段对比矩阵维度缺失补充缺失维度评分,无法评分则标注"数据不足"
人类决策超时未响应暂停编排流程,保留当前状态,等待人类决策后继续
上下文接近上限优先保留当前阶段内容,将已完成阶段的输出摘要为关键结论写入文件
阶段总结生成失败基于已完成的子Skill输出生成部分总结,缺失项标注"数据缺失",不阻塞编排完成

编排协议

编排协议遵循 orchestrator-protocol.md 统一标准。

Pipeline

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: "针对不达标项补充生成或重新深化"

阶段执行计划

调用 ideation-workshop

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个维度完整
模式: 🤖→👤

阶段总结(post_pipeline)

所有业务阶段执行完成后,必须立即生成阶段总结文档:

动作: 生成阶段总结
输入:
  所有子Skill输出: output/pm-design/ideation-workshop/
  人类决策记录: 本轮执行中的人类决策点及结果
输出: output/phase-reports/pm-design/ideation-orchestrator.md
验证: 阶段总结文档已生成,6项结构(执行概览/关键发现/决策记录/产出清单/风险与待办/下游衔接)均非空
下游衔接:
  primary:
    target: design-orchestrator
    reason: 创意发散完成,将创意方案转化为PRD
    input_mapping:
      ideation_output: "output/pm-design/ideation-workshop/ → design-prd输入"
  alternatives:
    - target: validation-orchestrator
      reason: 创意方案存在高风险假设,需先验证
      condition: 创意方案中关键假设风险等级≥高时
    - target: opportunity-orchestrator
      reason: 创意方向不明确,需回溯到机会定义
      condition: 创意收敛后仍无法形成明确产品方向时
  special_cases: []
模式: 🤖

⏸ 阶段卡口:阶段总结文档已生成且6项结构均非空 → 未通过:补充缺失结构项后重新生成

阶段卡口

卡口条件未通过处理
创意工作坊完成ideation-workshop输出文件已生成且非空针对不达标项补充生成或重新深化
阶段总结已生成output/phase-reports/pm-design/ideation-orchestrator.md 已生成且6项结构均非空补充缺失结构项后重新生成

人类决策点

决策点触发条件决策内容
方案最终选择创意工作坊收敛完成,对比矩阵已生成人类做最终方案选择,可接受AI推荐、调整优先级、组合方案或否决

变更记录

  • v1.0: 初始版本
  • v2.0: description触发词优化
  • v3.0: 编排器优化——新增子Skill执行协议、任务调度改为阶段执行计划、调度规则改为执行模式、阶段卡口和人类决策点改为表格、增加子Skill输入输出路径
  • v5.0: 编排协议重构——子Skill执行协议改为编排协议、新增Pipeline定义、阶段执行计划改为调用指令格式、删除调度规则
  • v6.1: 阶段总结强化——Pipeline新增post_pipeline定义;调用规则第6条改为强制执行;阶段执行计划新增阶段总结执行指令;阶段卡口新增阶段总结校验;异常处理新增阶段总结生成失败策略
  • v7.0: 子Skill合并——ideation-hmw/ideation-scamper/ideation-inversion/ideation-convergence合并为ideation-workshop;Pipeline stages从4个阶段简化为1个阶段;阶段执行计划、阶段卡口、人类决策点相应更新

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 625,857. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.