roadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
npx skills add deanpeters/Product-Manager-Skills --skill roadmap-planning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides product managers through strategic roadmap planning by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing into a structured process to move from disconnected feature requests to an outcome-driven roadmap.
How it works
The workflow unfolds in 5 phases:
- Phase 1: Gather Inputs (Day 1-2) — collect business goals, customer problems, technical constraints, and stakeholder requests to produce outputs: business outcomes, customer problems, technical investments, and stakeholder requests.
- Phase 2: Define Initiatives (Epics) (Day 3-4) — create epics with hypotheses, success metrics, and effort estimates; map each epic to a primary business outcome.
- Phase 3: Prioritize Initiatives (Day 5) — select a prioritization framework via interactive guidance, score epics, and adjust for strategic fit to produce a ranked backlog and top 10 epics.
- Phase 4: Sequence Roadmap (Day 6-7) — map dependencies and sequence epics into Now/Next/Later or by quarters; validate the sequence with engineering and produce a dependency map.
- Phase 5: Communicate Roadmap (Week 2) — create a roadmap presentation, present to stakeholders, gather feedback, refine to final roadmap, and publish internally or externally.
The workflow references other skills for specific steps (e.g., epic hypotheses and prioritization guidance) and uses a structured, phased approach to produce a cohesive roadmap.
When to use it
Use during annual or quarterly planning cycles, after a strategy session to translate strategy into a roadmap, or when onboarding stakeholders to align direction.
What it can touch
Involves inputs from business goals, customer problems, technical constraints, stakeholder requests, and outputs such as epics, prioritization scores, sequencing plans, dependency graphs, and a roadmap presentation.
Caveats
The guide emphasizes strategic roadmapping and communication rather than tactical sprint planning; roadmaps are described as plans that can evolve with learning, not contracts. No licensing or risk details are provided beyond workflow limitations mentioned in the described phases.
## Purpose 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. ## Input **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 defin
- Purpose
- Input
- Key Concepts
- What is Strategic Roadmap Planning?
- Types of Roadmaps
- Why This Works
- Anti-Patterns (What This Is NOT)
- When to Use This
- When NOT to Use This
- Facilitation Source of Truth
- Application
- Phase 1: Gather Inputs (Day 1-2)
- Activities
- Outputs from Phase 1
What does the roadmap-planning skill do?
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
How do I install it?
Run `npx skills add deanpeters/Product-Manager-Skills --skill roadmap-planning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.