transform-roadmap — Claude Code command: what it does, how to install
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.
MIT ★ 28,211 updated 2026-10-16
/plugin marketplace add phuryn/pm-skills
/plugin install pm-execution@pm-skillsWhat transform-roadmap 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.
What it helps with
- 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 for the agent
- Run
/transform-roadmapon 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.
How to install transform-roadmap
1Plugin marketplace
/plugin marketplace add phuryn/pm-skills/plugin install pm-execution@pm-skills2Manually: put the files in place
.claude/commands/transform-roadmap.mdCall it with /transform-roadmap. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/transform-roadmap.mdCall it with /prompts:transform-roadmap. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/transform-roadmap.prompt.mdManually: put the files in place
.gemini/commands/transform-roadmap.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about transform-roadmap
How do I install transform-roadmap in Claude Code?
Add the marketplace with /plugin marketplace add phuryn/pm-skills, then install the plugin with /plugin install pm-execution@pm-skills. The command file is .claude/commands/transform-roadmap.md.
What does transform-roadmap do?
It rewrites a feature-led plan around user or business outcomes. The command adds success measures, groups related features, and produces a Markdown roadmap.
What input formats does transform-roadmap support?
You can provide a feature list, backlog, roadmap document, spreadsheet, Gantt export, or a screenshot of a roadmap tool.
Source text
transform-roadmap.md · MIT
--- 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
© Paweł Huryn · MIT · phuryn/pm-skills