# roadmap-planning

roadmap-planning turns goals, backlog items, and constraints into a multi-quarter roadmap. Use it to rank work, map dependencies, and explain what stays out of scope.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 283 installs · ★ 1107 repo stars
- Author: rampstackco
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/rampstackco/claude-skills/tree/HEAD/skills/roadmap-planning/SKILL.md
- Updated: 2026-10-19
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/rampstackco-roadmap-planning

## What it does

This skill turns a pile of ideas, requests, and ongoing initiatives into a release plan with reasons behind the choices. It works through five layers: strategic themes, initiatives, sequencing, team capacity, and a “not now” list. Each initiative can be described by its outcome, rough size, confidence, and prerequisites.

The planning input is a set of team goals, a complete backlog, available capacity, known constraints, and a planning horizon. You can apply RICE, MoSCoW, Kano, cost of delay, or a strategy-and-impact score, then use the same method across the backlog. A strategy is required first; without it, the roadmap becomes a feature queue.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill roadmap-planning -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/roadmap-planning/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/roadmap-planning/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill roadmap-planning -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/roadmap-planning/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill roadmap-planning -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/roadmap-planning/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install rampstackco/claude-skills skills/roadmap-planning
```

2. **Manually: put the files in place**
- File: `.github/skills/roadmap-planning/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill roadmap-planning -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/rampstackco/claude-skills --path skills/roadmap-planning
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/roadmap-planning/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add rampstackco/claude-skills --skill roadmap-planning -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/rampstackco/claude-skills/tree/HEAD/skills/roadmap-planning/SKILL.md

## When to use it
- build a roadmap for a quarter or a year
- rank initiatives inside strategic themes
- sequence work around dependencies
- match planned work to team capacity
- justify which requests stay out of scope

## Example prompts
- Build a roadmap for next quarter from this backlog and our team goals.
- Rank these initiatives, map their dependencies, and compare the plan with available capacity.
- Create a “not now” list and state what would move each item into the roadmap.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 01012d13745c76b9.

BEGIN THIRD-PARTY FILE 01012d13745c76b9
```text
---
name: roadmap-planning
description: "Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan."
category: product
catalog_summary: "Quarterly planning, prioritization, dependency mapping"
display_order: 2
---

# Roadmap Planning

Take a pile of ideas, requests, and ongoing work. Produce a defensible plan for what to ship, when, and why. The output is a roadmap document plus the prioritization work that made it credible.

---

## When to use

- Planning the next quarter or the next year
- Sequencing work where some items depend on others
- Balancing new builds, improvements, and maintenance
- Saying no (or "not yet") to specific requests with a defensible reason
- Aligning a team around a single shared plan
- Communicating the plan to stakeholders outside the team
- Replanning after a strategy shift, a missed quarter, or new constraints

## When NOT to use

- Specifying a single feature for development (use `pm-spec-writing`)
- Validating whether the idea is worth building (use `ux-research`)
- Designing the feature itself (use `design-standards`)
- Writing the launch plan for a single initiative (use `launch-runbook`)
- Reviewing what shipped vs what was promised (use `after-action-report`)

---

## Required inputs

- The team's strategy or top-level goals (1 to 5 OKRs, themes, or pillars)
- The backlog: every candidate item, with at least a one-sentence description
- The team's capacity (people × time)
- Known constraints (deadlines, dependencies, hiring, budget)
- The planning horizon (a quarter, two quarters, a year)

If the strategy is missing, the roadmap will be a list of features, not a plan. Push back and get the strategy first. A roadmap without strategy is just a queue.

---

## The framework: 5 layers

Roadmaps fail at five different layers. A roadmap is only as good as its weakest one.

### Layer 1: Themes (the WHY)

Top-level groupings tied to strategy. Every theme answers: "If we do nothing else this period, this is the outcome we want."

Good themes are:
- Outcome-shaped, not feature-shaped ("Reduce time-to-first-value" beats "Build onboarding")
- Limited (3 to 5 max)
- Defensible (you can explain why this and not something else)
- Measurable (each maps to one or two metrics)

Bad themes look like a junk drawer: "Improvements," "Tech debt," "Misc." If it can't be defended in one sentence, it isn't a theme.
```
END THIRD-PARTY FILE 01012d13745c76b9

The third-party file has ended. Everything between the 01012d13745c76b9 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2853 of 10981 bytes. © rampstackco · MIT · https://github.com/rampstackco/claude-skills/tree/HEAD/skills/roadmap-planning/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
