Creating Outcome-Focused Product Roadmaps with PM Skills

PM Skills transforms feature lists into strategic outcome statements using a modular AI operating system that combines markdown-based skills with slash commands.

The phuryn/pm-skills repository provides a plugin-based framework for product management work. It enables teams to convert output-centric roadmaps into outcome-driven strategic documents through reusable knowledge modules and automated workflows.

What is PM Skills?

PM Skills functions as a modular AI operating system for product management tasks. The architecture organizes functionality into distinct plugins—such as pm-execution, pm-product-strategy, and others—each containing three core components:

• Skills – Reusable, markdown-based knowledge modules that encode specific PM frameworks or techniques
• Commands – Slash-style workflows that chain skills into complete end-to-end processes
• Plugin manifest – The .claude-plugin/plugin.json file that registers the plugin with Claude Code, Claude Cowork, Codex, or any skill-aware assistant

This modular design allows teams to install only the specific domains they need, or load the entire marketplace at once.

The Outcome-Roadmap Implementation

The outcome-focused roadmap functionality resides in the pm-execution plugin. This implementation combines a declarative skill definition with an interactive command interface.

Core Skill Definition

The methodology is defined in pm-execution/skills/outcome-roadmap/SKILL.md. This file contains the step-by-step thinking framework, the outcome statement template, and reference links to deeper product-strategy material. Because skills are pure markdown, they can be consumed by any AI assistant that reads the SKILL.md format, including Gemini, OpenCode, Cursor, and Kiro.

The Four-Phase Workflow

The skill implements a structured transformation process:

1. Accept input – Ingests any free-form list, document, spreadsheet, or screenshot
2. Gather context – Prompts for product goals, OKRs, target audience, and preferred output format
3. Transform – Applies the outcome-roadmap logic, rewriting each initiative using the template: "Enable [segment] to [desired outcome] so that [business impact]"
4. Emit result – Generates a ready-to-share markdown file with outcome statements, success metrics, and optional follow-up actions

Invoking the Transform Command

The user-facing entry point is the /transform-roadmap command, defined in pm-execution/commands/transform-roadmap.md. This command parses supplied feature lists, applies the skill logic, and produces structured roadmap documents.

Command Syntax Examples

After installing the plugin (claude plugin marketplace add phuryn/pm-skills), invoke the workflow using:

# Example 1 – Inline feature list

/transform-roadmap
Q1: Build advanced search filters
Q1: Add AI-powered recommendations
Q1: Redesign dashboard for faster insights

# Example 2 – Upload a roadmap document

/transform-roadmap [upload my-roadmap.xlsx]

# Example 3 – Follow-up options

# After the command completes, the system prompts:

Want me to add OKR alignment for each outcome? (yes/no)
Should I draft a stakeholder presentation of this roadmap? (yes/no)

Expected Output Structure

The command emits a markdown roadmap with outcome statements aligned to success metrics:

## Outcome-Focused Roadmap: MyProduct — Q1 2026

### Now (Current Quarter)

| Outcome                                    | Success Metric               | Key Initiatives                |
|-------------------------------------------|------------------------------|--------------------------------|
| Enable customers to find products 50% faster | Search-time ↓ 50%           | Advanced search filters        |
| Increase average order value 20%          | AOV ↑ 20%                    | AI-powered recommendations      |
| Help operators monitor systems 80% faster | Dashboard load ↓ 80%        | Dashboard redesign              |

Cross-Platform Compatibility

While the /transform-roadmap command is Claude-specific, the underlying skill is portable. On non-Claude platforms, teams can copy the outcome-roadmap skill folder and invoke the logic manually. The plugin manifest at pm-execution/.claude-plugin/plugin.json handles registration for Claude environments, but the markdown-based skill files remain universally readable.

Summary

• PM Skills provides a modular AI operating system for product management through the phuryn/pm-skills repository
• The outcome-roadmap feature lives in the pm-execution plugin, combining SKILL.md methodology with the /transform-roadmap command
• The four-phase workflow converts feature lists into outcome statements using the template: Enable [segment] to [outcome] so that [impact]
• Pure markdown skills ensure portability across AI assistants (Claude, Gemini, Cursor, etc.), while commands provide Claude-specific automation
• Output includes success metrics and optional OKR alignment for stakeholder communication

Frequently Asked Questions

What file contains the outcome-roadmap methodology?

The core methodology is defined in pm-execution/skills/outcome-roadmap/SKILL.md within the phuryn/pm-skills repository. This markdown file contains the step-by-step framework, outcome statement templates, and strategic context references.

How do I use the transform command without Claude?

While the /transform-roadmap command requires Claude Code or Claude Cowork, you can manually apply the skill on other platforms. Copy the outcome-roadmap skill folder and feed the SKILL.md content to Gemini, OpenCode, Cursor, or Kiro along with your feature list.

What is the outcome statement template format?

According to the PM Skills source code, the transformation follows this structure: "Enable [segment] to [desired outcome] so that [business impact]". This format shifts focus from output (what is being built) to outcome (what the user achieves).

Which plugin contains the outcome-roadmap feature?

The feature resides in the pm-execution plugin. This plugin contains both the skill definition (skills/outcome-roadmap/SKILL.md) and the command interface (commands/transform-roadmap.md), along with the plugin manifest at .claude-plugin/plugin.json.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}