roadmap-planning

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
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"
---


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

**Now/Next/Later Roadmap:**
- **Now:** Current quarter (committed)
- **Next:** Following quarter (high confidence)
- **Later:** Future exploration (low confidence)
- **Best for:** Agile teams, uncertainty, continuous discovery

**Theme-Based Roadmap:**
- Organize by strategic themes (e.g., "Retention," "Enterprise Expansion," "Mobile Experience")
- **Best for:** Communicating to execs, showing strategic intent

**Timeline Roadmap (Quarters):**
- Q1: Epics A, B; Q2: Epics C, D; Q3: Epics E, F
- **Best for:** Resource planning, stakeholder communication

**Feature-Based Roadmap (Anti-Pattern):**
- Lists features without context (e.g., "Dark mode," "SSO," "Advanced reporting")
- **Why it fails:** No strategic narrative, no customer problems framed

### Why This Works
- **Outcome-driven:** Ties initiatives to business/customer outcomes
- **Stakeholder alignment:** Transparent process reduces political fr