원클릭으로
validation-assumption-map
当需要提取和评估产品假设时使用。假设地图自动生成工具,根据方案设计和PRD,自动提取价值假设、可行性假设、可用性假设、增长假设,并进行风险评估和验证方法推荐。关键词:假设提取、风险评估、假设地图、验证方法、假设梳理、风险假设。
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
当需要提取和评估产品假设时使用。假设地图自动生成工具,根据方案设计和PRD,自动提取价值假设、可行性假设、可用性假设、增长假设,并进行风险评估和验证方法推荐。关键词:假设提取、风险评估、假设地图、验证方法、假设梳理、风险假设。
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 | validation-assumption-map |
| description | 当需要提取和评估产品假设时使用。假设地图自动生成工具,根据方案设计和PRD,自动提取价值假设、可行性假设、可用性假设、增长假设,并进行风险评估和验证方法推荐。关键词:假设提取、风险评估、假设地图、验证方法、假设梳理、风险假设。 |
| metadata | {"module":"产品构思与设计","sub-module":"方案验证","type":"pipeline","version":"2.1","domain_tags":["互联网","软件","通用"],"trigger_examples":["产品有哪些假设没验证","帮我梳理假设和风险","哪些假设可能不成立"],"interaction_mode":"ai_suggest_human_approve"} |
| execution_depth | {"default":"standard","quick_description":"直接输出核心假设和验证优先级","deep_description":"完整假设地图 + 验证实验设计 + 风险量化评估 + 假设演进追踪"} |
| 属性 | 值 |
|---|---|
| Pipeline ID | 10 |
| 名称 | 假设地图自动生成 |
| 执行模式 | 🤖→👤 AI建议人类审批 |
| 输入 | 方案设计输出 + PRD |
🤖→👤 AI建议人类审批
| 输入项 | 类型 | 必填 | 来源 | 说明 |
|---|---|---|---|---|
| 方案设计输出 | JSON | 是 | output/pm-design/design-prototype / output/pm-design/design-userflow | 功能列表、用户旅程、交互设计说明 |
| PRD | markdown | 是 | output/pm-design/design-prd/prd.md | 问题陈述、目标用户、核心价值主张 |
| PRD结构化数据 | JSON | ○ | output/pm-design/design-prd/prd.json | PRD机器可消费版本,包含features[],供假设提取对齐 |
{
"solution_design": {
"features": ["功能1", "功能2", ...],
"user_journey": "用户旅程描述",
"interaction_design": "交互设计说明"
},
"prd": {
"problem_statement": "问题陈述",
"target_users": "目标用户",
"core_value": "核心价值主张"
}
}
对每个功能点,提取以下四类假设:
| 假设类型 | 定义 | 示例 |
|---|---|---|
| 价值假设 | 用户是否认可该功能价值 | 用户愿意为XX功能付费 |
| 可行性假设 | 技术/资源是否支撑实现 | 我们能够实现XX功能 |
| 可用性假设 | 用户是否能顺利使用 | 用户能理解XX的操作方式 |
| 增长假设 | 该功能是否能驱动增长 | XX功能能带来用户留存提升 |
规则: 每个功能点 → 至少1个假设
对每个假设进行风险评估:
| 维度 | 评分 | 说明 |
|---|---|---|
| 影响度 (Impact) | 1-5 | 假设不成立对产品的影响程度 |
| 不确定性 (Uncertainty) | 1-5 | 假设成立概率的不确定程度 |
风险分数计算: risk_score = impact × uncertainty
| 风险等级 | 分数范围 | 标识 |
|---|---|---|
| 高风险 | 15-25 | is_max_risk = true |
| 中风险 | 8-14 | is_max_risk = false |
| 低风险 | 1-7 | is_max_risk = false |
根据假设类型,推荐验证方法:
| 假设类型 | 推荐验证方法 |
|---|---|
| 价值假设 | 落地页测试、预售MVP、用户访谈、付费意愿调研 |
| 可行性假设 | 技术原型、成本估算、专家评审 |
| 可用性假设 | 原型测试、可用性测试、任务完成率分析 |
| 增长假设 | A/B测试、数据分析、用户行为追踪 |
| 深度级别 | 输出范围 | 说明 |
|---|---|---|
| quick | 核心假设和验证优先级 | 核心结论 + 最小可行产物 |
| standard | 完整产物(当前默认) | 完整产物,包含全部Step输出 |
| deep | 完整假设地图 + 验证实验设计 + 风险量化评估 + 假设演进追踪 | 完整产物 + 扩展分析 + 深度推演 |
存储路径:output/pm-design/validation-assumption-map/
输出文件:assumption_map.json
{
"assumption_map": [
{
"id": "A001",
"feature_id": "F001",
"type": "value|feasibility|usability|growth",
"assumption": "假设内容描述",
"impact": 4,
"uncertainty": 4,
"risk_score": 16,
"is_max_risk": false,
"validation_method": "推荐验证方法",
"validation_metric": "验证指标"
}
],
"summary": {
"total_assumptions": 12,
"max_risk_assumptions": ["A005", "A008"],
"assumption_coverage": "100%"
}
}
| 字段 | 类型 | 说明 |
|---|---|---|
| id | string | 假设唯一标识 |
| feature_id | string | 关联的功能点ID |
| type | enum | 假设类型 |
| assumption | string | 假设内容 |
| impact | number | 影响度评分(1-5) |
| uncertainty | number | 不确定性评分(1-5) |
| risk_score | number | 风险分数(1-25) |
| is_max_risk | boolean | 是否为最大风险假设 |
| validation_method | string | 推荐验证方法 |
| validation_metric | string | 验证指标 |
输出校验规则:详见下方输出校验规则章节
最大风险假设识别
假设验证方法
| 缺失的上游输入 | 降级方案 | 输出影响 | 数据获取说明 |
|---|---|---|---|
| 方案设计数据缺失 | 用户提供方案描述,提取假设 | 缺乏结构化方案数据,假设覆盖可能不全 | 要求用户提供方案描述或上传design-prototype/design-userflow文件 |
| PRD文档缺失 | 用户提供方案描述,提取假设 | 缺乏PRD数据,假设与需求可能脱节 | 要求用户提供功能需求描述或上传prd.json文件 |
| 方案设计+PRD均缺失 | 用户提供方案描述,提取假设 | 整体置信度降低,假设可能不够完整 | 要求用户提供核心假设和功能需求描述 |
| 所有上游文件均缺失 | 提示用户先执行前序阶段,或基于用户方案描述提取假设 | 输出仅为基本假设列表 | 要求用户提供核心假设、用户痛点和功能需求 |
| 字段路径 | 类型 | 必填 | 说明 |
|---|---|---|---|
| assumption_map | array | 是 | 假设列表 |
| assumption_map[].id | string | 是 | 假设唯一标识 |
| assumption_map[].feature_id | string | 是 | 关联功能点ID |
| assumption_map[].type | string | 是 | 假设类型(value/feasibility/usability/growth) |
| assumption_map[].assumption | string | 是 | 假设内容 |
| assumption_map[].impact | number | 是 | 影响度评分(1-5) |
| assumption_map[].uncertainty | number | 是 | 不确定性评分(1-5) |
| assumption_map[].risk_score | number | 是 | 风险分数(1-25) |
| assumption_map[].is_max_risk | boolean | 是 | 是否为最大风险假设 |
| assumption_map[].validation_method | string | 是 | 推荐验证方法 |
| assumption_map[].validation_metric | string | 是 | 验证指标 |
| summary | object | 是 | 统计摘要 |
| summary.total_assumptions | integer | 是 | 假设总数 |
| summary.max_risk_assumptions | array | 是 | 最大风险假设ID列表 |
| 上游变更 | 影响范围 | 响应策略 |
|---|---|---|
| 方案设计功能增删 | 假设提取、风险评估 | 标注受影响的功能点,建议人类确认是否重新提取假设 |
| PRD核心价值变更 | 价值假设 | 标注受影响的价值假设,建议人类确认是否重新评估 |
| 原型交互变更 | 可用性假设 | 标注受影响的可用性假设,建议人类确认是否重新评估 |
| 假设地图变更类型 | 通知范围 | 通知方式 |
|---|---|---|
| 假设增删 | validation-mvp、validation-experiment | 标记假设变更,触发MVP范围和实验设计更新 |
| 风险评分变更 | validation-mvp、validation-experiment | 标记评分变更,触发MVP Must Have和实验优先级更新 |
| 验证方法变更 | validation-experiment | 标记方法变更,触发实验方案更新 |
输入:
功能点: 智能推荐
PRD核心价值: 帮助用户快速发现感兴趣的内容
输出:
{
"assumption_map": [
{
"id": "A001",
"feature_id": "F001",
"type": "value",
"assumption": "用户认为智能推荐能帮助其发现感兴趣的内容",
"impact": 4,
"uncertainty": 4,
"risk_score": 16,
"is_max_risk": true,
"validation_method": "用户访谈",
"validation_metric": "推荐内容点击率>15%"
},
{
"id": "A002",
"feature_id": "F001",
"type": "usability",
"assumption": "用户能理解推荐结果的来源和含义",
"impact": 3,
"uncertainty": 3,
"risk_score": 9,
"is_max_risk": false,
"validation_method": "原型测试",
"validation_metric": "任务完成率>80%"
}
]
}