roadmap-planning by deanpeters/product-manager-skills
npx skills add https://github.com/deanpeters/product-manager-skills --skill roadmap-planning通过将优先级排序、史诗定义、利益相关者对齐和发布排序等技能整合到一个结构化流程中,指导产品经理进行战略路线图规划。使用此方法,将零散的功能请求转变为连贯的、以结果为导向的路线图,该路线图能对齐利益相关者、逻辑地安排工作顺序并传达战略意图——避免缺乏战略叙事或以客户为中心的框架的“功能工厂”式路线图。
这不是甘特图——它是一种战略沟通工具,展示你正在构建什么、它为何重要以及它如何促成业务成果。
路线图规划是以下过程:
现在/下一步/未来路线图:
基于主题的路线图:
时间线路线图(季度):
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
当将此工作流作为引导对话运行时,请使用 workshop-facilitation 作为交互协议。
它定义了:
其他(请指定))此文件定义了工作流序列和特定领域的输出。如果存在冲突,请遵循此文件的工作流逻辑。
使用 template.md 获取完整的填写结构。
此工作流在 1-2 周 内编排 5 个阶段,使用多个组件和交互式技能。
目标: 收集业务目标、客户问题、技术限制、利益相关者请求。
1. 审查业务目标(OKRs,战略举措)
2. 审查客户问题(探索洞察)
skills/discovery-process/SKILL.md 的洞察(如果最近完成)3. 审查技术限制与机遇
4. 审查利益相关者请求
目标: 将输入转化为具有假设、成功指标和工作量估算的史诗。
1. 定义史诗假设
skills/epic-hypothesis/SKILL.md(组件)史诗示例(SaaS 产品):
Epic 1: Guided Onboarding
Hypothesis: We believe that adding a step-by-step onboarding checklist for non-technical users will increase activation rate from 40% to 60% because users currently drop off due to lack of guidance.
Success Metric: Activation rate (% completing first action within 24 hours)
Target: 40% → 60%
Epic 2: Enterprise SSO
Hypothesis: We believe that adding SSO for enterprise accounts will increase enterprise deals closed from 2/quarter to 5/quarter because enterprise buyers require SSO for security compliance.
Success Metric: Enterprise deals closed per quarter
Target: 2 → 5
Epic 3: Mobile-Optimized Workflows
Hypothesis: We believe that optimizing core workflows for mobile will increase mobile DAU from 5% to 20% because mobile-first users currently can't complete workflows on the go.
Success Metric: Mobile DAU as % of total DAU
Target: 5% → 20%
2. 估算工作量(T恤尺码法)
3. 映射到业务成果
目标: 根据影响、工作量和战略契合度对史诗进行排序。
1. 选择优先级排序框架
skills/prioritization-advisor/SKILL.md(交互式)2. 为史诗评分
| Epic | Reach | Impact | Confidence | Effort | RICE Score |
|---|---|---|---|---|---|
| Guided Onboarding | 10,000 users | 3 (massive) | 80% | 1 month | 24,000 |
| Enterprise SSO | 500 users | 3 (massive) | 90% | 2 months | 675 |
| Mobile Workflows | 5,000 users | 2 (high) | 60% | 3 months | 2,000 |
| Advanced Reporting | 2,000 users | 2 (high) | 50% | 2 months | 1,000 |
3. 根据战略契合度进行调整
目标: 将史诗按逻辑依赖关系组织到季度/发布中。
1. 映射依赖关系
2. 按季度(或发布)排序
路线图示例(基于时间线):
Q1 2026 (Now - Committed):
├─ Guided Onboarding (Retention)
├─ Enterprise SSO (Acquisition)
└─ Mobile-Optimized Workflows (Engagement)
Q2 2026 (Next - High Confidence):
├─ Advanced Reporting (depends on Data Pipeline, Q1)
├─ Slack Integration (Engagement)
└─ Pricing Page Redesign (Acquisition)
Q3 2026 (Later - Lower Confidence):
├─ Mobile App (depends on API Redesign)
├─ AI-Powered Recommendations
└─ Multi-Language Support
Q4 2026 (Exploration):
├─ Marketplace/Plugin Ecosystem
└─ Enterprise Onboarding Concierge
替代方案:现在/下一步/未来路线图
NOW (Current Quarter):
- Guided Onboarding
- Enterprise SSO
- Mobile-Optimized Workflows
NEXT (Following Quarter):
- Advanced Reporting
- Slack Integration
- Pricing Page Redesign
LATER (Future):
- Mobile App
- AI Recommendations
- Multi-Language Support
3. 与工程团队验证
目标: 向利益相关者展示路线图,收集反馈,建立共识。
1. 创建路线图演示文稿
2. 向利益相关者展示
3. 收集反馈
4. 完善路线图
5. 发布路线图
Week 1:
├─ Day 1-2: Gather Inputs
│ ├─ Review business goals (OKRs)
│ ├─ Review customer problems (discovery insights)
│ ├─ Review technical constraints
│ └─ Review stakeholder requests
│
├─ Day 3-4: Define Initiatives (Epics)
│ ├─ skills/epic-hypothesis/SKILL.md (60 min per epic)
│ ├─ Estimate effort (90 min)
│ └─ Map to business outcomes
│
├─ Day 5: Prioritize Initiatives
│ ├─ skills/prioritization-advisor/SKILL.md (30 min)
│ ├─ Score epics (120 min)
│ └─ Adjust for strategic fit
│
└─ Day 6-7: Sequence Roadmap
├─ Map dependencies
├─ Sequence by quarter (Q1, Q2, Q3)
└─ Validate with engineering
Week 2:
└─ Communicate Roadmap
├─ Create presentation (2-3 hours)
├─ Present to stakeholders (60 min)
├─ Gather feedback
├─ Refine roadmap (1-2 days)
└─ Publish roadmap
总时间投入:
完整路线图示例请参见 examples/sample.md。
迷你示例摘录:
Now: Guided onboarding (activation +20%)
Next: Enterprise SSO (deal velocity)
Later: Mobile workflows (DAU lift)
症状: 路线图列出没有上下文的功能(“深色模式”、“SSO”、“高级过滤器”)
后果: 缺乏战略清晰度,利益相关者不理解“为什么”
解决方法: 将史诗框定为具有成功指标的假设(不仅仅是功能名称)
症状: 高管决定路线图,没有数据驱动的优先级排序
后果: 构建错误的东西,忽视客户问题
解决方法: 使用优先级排序框架(RICE, ICE)透明地为史诗评分
症状: 路线图被视为合同,没有调整的灵活性
后果: 当学到新信息时无法调整方向
解决方法: 将路线图沟通为“战略计划,根据学习成果可能变更”
症状: 未检查技术依赖关系就对史诗进行排序
后果: Q2 的史诗因 Q1 的依赖项未完成而受阻
解决方法: 在阶段 4 明确映射依赖关系,并与工程团队验证
症状: 产品经理独自创建路线图,展示完成的计划
后果: 没有认同感,利益相关者感到被排除在外
解决方法: 从所有利益相关者处收集输入(阶段 1),展示草案(阶段 5)以获取反馈
阶段 2:
skills/epic-hypothesis/SKILL.md(组件)阶段 3:
skills/prioritization-advisor/SKILL.md(交互式)阶段 4:
阶段 5:
可选/相关:
skills/product-strategy-session/SKILL.md(工作流)—— 在路线图规划之前运行以建立战略skills/discovery-process/SKILL.md(工作流)—— 为阶段 1 提供客户问题输入skills/user-story-mapping-workshop/SKILL.md(交互式)—— 用于需要发布规划的复杂史诗技能类型: 工作流 建议文件名: roadmap-planning.md 建议放置位置: /skills/workflows/ 依赖项: 编排 skills/epic-hypothesis/SKILL.md, skills/prioritization-advisor/SKILL.md,以及手动活动
每周安装次数
597
代码库
GitHub 星标
2.3K
首次出现
Feb 12, 2026
安全审计
安装于
codex553
opencode545
github-copilot541
gemini-cli540
cursor539
kimi-cli536
Guide product managers through strategic roadmap planning by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing skills into a structured process. Use this to move from disconnected feature requests to a cohesive, outcome-driven roadmap that aligns stakeholders, sequences work logically, and communicates strategic intent—avoiding "feature factory" roadmaps that lack strategic narrative or customer-centric framing.
This is not a Gantt chart—it's a strategic communication tool that shows what you're building, why it matters, and how it ladders up to business outcomes.
Roadmap planning is the process of:
Now/Next/Later Roadmap:
Theme-Based Roadmap:
Timeline Roadmap (Quarters):
Feature-Based Roadmap (Anti-Pattern):
When running this workflow as a guided conversation, use workshop-facilitation as the interaction protocol.
It defines:
Other (specify) when useful)This file defines the workflow sequence and domain-specific outputs. If there is a conflict, follow this file's workflow logic.
Use template.md for the full fill-in structure.
This workflow orchestrates 5 phases over 1-2 weeks , using multiple component and interactive skills.
Goal: Collect business goals, customer problems, technical constraints, stakeholder requests.
1. Review Business Goals (OKRs, Strategic Initiatives)
2. Review Customer Problems (Discovery Insights)
skills/discovery-process/SKILL.md (if recently completed)3. Review Technical Constraints & Opportunities
4. Review Stakeholder Requests
Goal: Turn inputs into epics with hypotheses, success metrics, and effort estimates.
1. Define Epic Hypotheses
skills/epic-hypothesis/SKILL.md (component)Example Epics (SaaS Product):
Epic 1: Guided Onboarding
Hypothesis: We believe that adding a step-by-step onboarding checklist for non-technical users will increase activation rate from 40% to 60% because users currently drop off due to lack of guidance.
Success Metric: Activation rate (% completing first action within 24 hours)
Target: 40% → 60%
Epic 2: Enterprise SSO
Hypothesis: We believe that adding SSO for enterprise accounts will increase enterprise deals closed from 2/quarter to 5/quarter because enterprise buyers require SSO for security compliance.
Success Metric: Enterprise deals closed per quarter
Target: 2 → 5
Epic 3: Mobile-Optimized Workflows
Hypothesis: We believe that optimizing core workflows for mobile will increase mobile DAU from 5% to 20% because mobile-first users currently can't complete workflows on the go.
Success Metric: Mobile DAU as % of total DAU
Target: 5% → 20%
2. Estimate Effort (T-Shirt Sizing)
3. Map to Business Outcomes
Goal: Rank epics by impact, effort, and strategic fit.
1. Choose Prioritization Framework
skills/prioritization-advisor/SKILL.md (interactive)2. Score Epics
| Epic | Reach | Impact | Confidence | Effort | RICE Score |
|---|---|---|---|---|---|
| Guided Onboarding | 10,000 users | 3 (massive) | 80% | 1 month | 24,000 |
| Enterprise SSO | 500 users | 3 (massive) | 90% | 2 months | 675 |
| Mobile Workflows | 5,000 users | 2 (high) | 60% | 3 months | 2,000 |
| Advanced Reporting | 2,000 users | 2 (high) | 50% | 2 months | 1,000 |
3. Adjust for Strategic Fit
Goal: Organize epics into quarters/releases with logical dependencies.
1. Map Dependencies
2. Sequence by Quarter (or Release)
Example Roadmap (Timeline-Based):
Q1 2026 (Now - Committed):
├─ Guided Onboarding (Retention)
├─ Enterprise SSO (Acquisition)
└─ Mobile-Optimized Workflows (Engagement)
Q2 2026 (Next - High Confidence):
├─ Advanced Reporting (depends on Data Pipeline, Q1)
├─ Slack Integration (Engagement)
└─ Pricing Page Redesign (Acquisition)
Q3 2026 (Later - Lower Confidence):
├─ Mobile App (depends on API Redesign)
├─ AI-Powered Recommendations
└─ Multi-Language Support
Q4 2026 (Exploration):
├─ Marketplace/Plugin Ecosystem
└─ Enterprise Onboarding Concierge
Alternative: Now/Next/Later Roadmap
NOW (Current Quarter):
- Guided Onboarding
- Enterprise SSO
- Mobile-Optimized Workflows
NEXT (Following Quarter):
- Advanced Reporting
- Slack Integration
- Pricing Page Redesign
LATER (Future):
- Mobile App
- AI Recommendations
- Multi-Language Support
3. Validate with Engineering
Goal: Present roadmap to stakeholders, gather feedback, build alignment.
1. Create Roadmap Presentation
2. Present to Stakeholders
3. Gather Feedback
4. Refine Roadmap
5. Publish Roadmap
Week 1:
├─ Day 1-2: Gather Inputs
│ ├─ Review business goals (OKRs)
│ ├─ Review customer problems (discovery insights)
│ ├─ Review technical constraints
│ └─ Review stakeholder requests
│
├─ Day 3-4: Define Initiatives (Epics)
│ ├─ skills/epic-hypothesis/SKILL.md (60 min per epic)
│ ├─ Estimate effort (90 min)
│ └─ Map to business outcomes
│
├─ Day 5: Prioritize Initiatives
│ ├─ skills/prioritization-advisor/SKILL.md (30 min)
│ ├─ Score epics (120 min)
│ └─ Adjust for strategic fit
│
└─ Day 6-7: Sequence Roadmap
├─ Map dependencies
├─ Sequence by quarter (Q1, Q2, Q3)
└─ Validate with engineering
Week 2:
└─ Communicate Roadmap
├─ Create presentation (2-3 hours)
├─ Present to stakeholders (60 min)
├─ Gather feedback
├─ Refine roadmap (1-2 days)
└─ Publish roadmap
Total Time Investment:
See examples/sample.md for full roadmap examples.
Mini example excerpt:
Now: Guided onboarding (activation +20%)
Next: Enterprise SSO (deal velocity)
Later: Mobile workflows (DAU lift)
Symptom: Roadmap lists features ("Dark mode," "SSO," "Advanced filters") with no context
Consequence: No strategic clarity, stakeholders don't understand "why"
Fix: Frame epics as hypotheses with success metrics (not just feature names)
Symptom: Execs dictate roadmap, no data-driven prioritization
Consequence: Build wrong things, ignore customer problems
Fix: Use prioritization framework (RICE, ICE) to transparently score epics
Symptom: Roadmap treated as contract, no flexibility to adjust
Consequence: Can't pivot when you learn new information
Fix: Communicate roadmap as "strategic plan, subject to change based on learning"
Symptom: Sequence epics without checking technical dependencies
Consequence: Q2 epic blocked because Q1 dependency didn't finish
Fix: Map dependencies explicitly in Phase 4, validate with engineering
Symptom: PM creates roadmap alone, presents finished plan
Consequence: No buy-in, stakeholders feel excluded
Fix: Gather inputs (Phase 1) from all stakeholders, present draft (Phase 5) for feedback
Phase 2:
skills/epic-hypothesis/SKILL.md (component)Phase 3:
skills/prioritization-advisor/SKILL.md (interactive)Phase 4:
Phase 5:
Optional/Related:
skills/product-strategy-session/SKILL.md (workflow) — Run before roadmap planning to establish strategyskills/discovery-process/SKILL.md (workflow) — Provides customer problem inputs for Phase 1skills/user-story-mapping-workshop/SKILL.md (interactive) — For complex epics requiring release planningSkill type: Workflow Suggested filename: roadmap-planning.md Suggested placement: /skills/workflows/ Dependencies: Orchestrates skills/epic-hypothesis/SKILL.md, skills/prioritization-advisor/SKILL.md, plus manual activities
Weekly Installs
597
Repository
GitHub Stars
2.3K
First Seen
Feb 12, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
codex553
opencode545
github-copilot541
gemini-cli540
cursor539
kimi-cli536
Google Workspace CLI 团队负责人技能:自动化站会、任务协调与团队沟通工具
6,100 周安装
OpenAPI 转 TypeScript 工具 - 自动生成 API 接口与类型守卫
563 周安装
数据库模式设计器 - 内置最佳实践,自动生成生产级SQL/NoSQL数据库架构
564 周安装
Rust Unsafe代码检查器 - 安全使用Unsafe Rust的完整指南与最佳实践
564 周安装
.NET并发编程模式指南:async/await、Channels、Akka.NET选择决策树
565 周安装
韩语语法检查器 - 基于国立国语院标准的拼写、空格、语法、标点错误检测与纠正
565 周安装
技能安全扫描器 - 检测Claude技能安全漏洞,防范提示注入与恶意代码
565 周安装