# Roadmap Planning

Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment...

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill roadmap-planning -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill roadmap-planning -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill roadmap-planning -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill roadmap-planning -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## 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 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.`

## Key Concepts

### What is Strategic Roadmap Planning?

Roadmap planning is the process of:
1. **Gathering inputs**, Customer problems, business goals, technical constraints
2. **Defining initiatives**, Epics with clear hypotheses and success metrics
3. **Prioritizing**, Rank initiatives by impact, effort, strategic fit
4. **Sequencing**, Organize into releases/quarters with logical dependencies
5. **Communicating**, Present roadmap to stakeholders with strategic narrative

### Types of Roadmaps

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/roadmap-planning/SKILL.md