# transform-roadmap

transform-roadmap is a Claude Code command that turns a feature list or existing roadmap into an outcome-led plan with success measures and strategic context for product planning.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 28211 repo stars
- Author: Paweł Huryn
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/phuryn/pm-skills/tree/HEAD/pm-execution/commands/transform-roadmap.md
- Updated: 2026-10-16
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/transform-roadmap

## What it does

\`transform-roadmap` takes a feature list, backlog, or existing roadmap and reshapes it around outcomes. It can work from pasted text, a document, spreadsheet, Gantt export, or roadmap screenshot. The command extracts timing and context, then asks about product goals, the roadmap audience, and the preferred layout.

For each item, it identifies the user or business result behind the work, writes an outcome statement, adds a success measure, and groups related features into one initiative. The generated plan can use Now/Next/Later, quarterly sections, or a timeline, with transformation notes and a Markdown output file.

The command runs in Claude Code through `pm-execution@pm-skills`. Strategic goals, audience, and format shape the follow-up questions, so a bare feature list will lead to more clarification before the roadmap is produced.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add phuryn/pm-skills
```
In the agent chat (not a shell):
```text
/plugin install pm-execution@pm-skills
```

2. **Manually: put the files in place**
- File: `.claude/commands/transform-roadmap.md` — Call it with /transform-roadmap. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/transform-roadmap.md` — Call it with /prompts:transform-roadmap. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/transform-roadmap.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/transform-roadmap.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/phuryn/pm-skills/tree/HEAD/pm-execution/commands/transform-roadmap.md

## When to use it
- turn a feature backlog into an outcome-based roadmap
- connect initiatives to user or business results
- define success measures for roadmap items
- group features that support the same outcome
- format a plan as Now/Next/Later

## Example prompts
- Run `/transform-roadmap` on this feature list and rewrite it as an outcome-focused roadmap.
- Process the uploaded roadmap, ask for the product goals and audience, then produce a Now/Next/Later version.
- Convert this plan into a Markdown roadmap with outcomes, success measures, and grouped initiatives.

## Source text · transform-roadmap.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: 6c0537189d989563.

BEGIN THIRD-PARTY FILE 6c0537189d989563
````text
---
description: Convert a feature-based roadmap into an outcome-focused roadmap that communicates strategic intent
argument-hint: "<roadmap as text, file, or list of planned features>"
---

# /transform-roadmap -- Outcome-Focused Roadmap

Take a list of planned features or an output-focused roadmap and rewrite it as an outcome-focused roadmap that communicates *why* instead of *what*.

## Invocation

```
/transform-roadmap [paste your feature list or roadmap]
/transform-roadmap [upload a roadmap doc, spreadsheet, or screenshot]
```

## Workflow

### Step 1: Accept the Current Roadmap

Accept in any format:
- Feature list or backlog items
- Roadmap document (Now/Next/Later, quarterly, timeline)
- Spreadsheet or Gantt chart export
- Screenshot of a roadmap tool

Parse each item to extract: feature name, description, target date/timeframe, and any context.

### Step 2: Understand Strategic Context

Ask:
- What are the product goals or OKRs for this period?
- Who is the audience for this roadmap? (execs, engineering, customers, board)
- What format do you prefer? (Now/Next/Later, quarterly, timeline)

### Step 3: Transform Each Item

Apply the **outcome-roadmap** skill:

For each feature/output on the roadmap:
1. Identify the **user or business outcome** it's trying to achieve
2. Rewrite as an outcome statement: "[Verb] [metric/experience] for [user segment]"
3. Group features that serve the same outcome under one initiative
4. Add success metrics to each outcome

**Before → After examples:**
- "Build SSO integration" → "Reduce enterprise onboarding friction — target: 50% faster time-to-first-value for enterprise accounts"
- "Redesign dashboard" → "Help power users find insights faster — target: 30% reduction in time-to-insight"
- "Add CSV export" → "Enable teams to share data outside the product — target: 25% increase in report sharing"

### Step 4: Generate Transformed Roadmap

```
## Outcome-Focused Roadmap: [Product] — [Period]

**Strategic themes**: [2-3 high-level themes]

### Now (Current Quarter)
**Theme: [Strategic Theme]**
| Outcome | Success Metric | Key Initiatives | Status |
|---------|---------------|----------------|--------|

### Next (Next Quarter)
**Theme: [Strategic Theme]**
| Outcome | Success Metric | Key Initiatives | Confidence |
|---------|---------------|----------------|------------|

### Later (Future)
**Theme: [Strategic Theme]**
| Outcome | Success Metric | Key Initiatives | Dependencies |
|---------|---------------|----------------|-------------|

### Transformation Notes
| Original Feature | Transformed Outcome | Why This Framing |
|-----------------|--------------------|-----------------|

### What Changed
[Summary of how the roadmap narrative shifted]
```

Save as a markdown file.

### Step 5: Review

Offer:
- "Want me to **add OKR alignment** for each outcome?"
- "Should I **draft a stakeholder presentation** of this roadmap?"
- "Want me to **identify risks** for the Now items?"

## Notes

- Outcomes should be measurable and have a clear "done" state
- Multiple features can map to one outcome — this is a feature, not a bug
- If an output doesn't clearly serve an outcome, flag it for the user to justify or deprioritize
- The audience matters: exec roadmaps should be outcome-only, engineering roadmaps can include deliverables under each outcome
- "Later" items should be less specific — outcomes without committed solutions
````
END THIRD-PARTY FILE 6c0537189d989563

The third-party file has ended. Everything between the 6c0537189d989563 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.

© Paweł Huryn · MIT · https://github.com/phuryn/pm-skills/tree/HEAD/pm-execution/commands/transform-roadmap.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
