메뉴
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill roadmap-planning명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | roadmap-planning |
| argument-hint | [product and planning horizon] |
| description | Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute. |
| intent | 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. |
| type | workflow |
| theme | strategy-positioning |
| best_for | ["Building a strategic roadmap that survives exec review","Prioritizing competing initiatives across multiple teams","Planning and sequencing work for the next quarter or half-year"] |
| scenarios | ["I have 15 competing initiatives and need to build a Q2 roadmap my exec team will actually approve","I'm planning our 6-month product roadmap and need to sequence work across 3 teams"] |
| estimated_time | 45-90 min |
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.
Works best with: The product and planning horizon (next quarter, next year). Also useful: Strategy or OKRs to ladder to, the candidate initiative list, team capacity, and known stakeholder pressures.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The workflow starts by establishing strategic context, then moves through prioritization, epic definition, and sequencing.
Example invocation: Plan a 2-quarter roadmap for our mobile app: here are our 3 OKRs and a list of 12 candidate initiatives.
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
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.
SOC 직업 분류 기준
