outcome-roadmap
- Use it when:
- Your roadmap lists features and you want it to say what each will change for customers and the business.
- It does:
- Asks of each initiative what outcome it serves, which customer problem it solves and which metric moves, then rewrites it.
- Format:
- Enable [customer segment] to [desired customer outcome] so that [business impact].
- You get:
- The roadmap by quarter or phase, each initiative beside its outcome statement, success metrics and sequencing notes, plus strategic context.
- Writes:
- Outcome-Roadmap-[year].md when the result is substantial.
TL;DR
From the PM Skills marketplace's pm-execution plugin. Feature-list roadmaps, it argues, create false precision and align teams on output instead of results. The agent reads your current roadmap and, if you mention strategy documents or company objectives, searches the web to see how the roadmap should line up with them. For each initiative it names the planned output, asks why it's being built and what changes for customers or the business, considers whether there's a better way to reach the same outcome, and rewrites it as an outcome statement. Its example turns "build advanced search filters" into "enable customers to find products 50% faster through intuitive discovery". The result lists the original initiatives by quarter or phase beside their outcomes, the metrics that will show success, and dependencies, then adds how the outcomes align with company strategy, key assumptions about customer needs, and flexible release windows in quarters rather than dates. Outcomes should be testable and measurable; when it's unclear what a feature drives, it keeps asking "so what?" until it reaches real customer or business value.
Summarizes the skill at 2a12295.
npx skills add https://github.com/phuryn/pm-skills --skill outcome-roadmap skills.sh pageSource on GitHubAll skills from phuryn/pm-skills
Fewer weekly downloads than 83% of skills
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 108 |
| Sep 28 | 86 |
| Oct 5 | 82 |
| Oct 12 | 74 |
| Oct 19 | 75 |
| Oct 26 | 132 |
| Nov 2 | 95 |
| Nov 9 | 86 |
More downloads than 51% of skills
More stars than 70% of repos
Older than 56% of skills
| Category |
Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A one-shot action you invoke by name, such as turning the conversation into a PRD. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From phuryn/pm-skills at 2a12295. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: outcome-roadmap
description: "Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes."Transform Roadmap to Outcome-Focused Format
Purpose
You are an experienced product manager helping $ARGUMENTS shift from output-focused roadmaps (which emphasize features) to outcome-focused roadmaps (which emphasize customer and business impact). This skill rewrites initiatives as outcome statements that inspire and measure what matters.
Context
Output-focused roadmaps create false precision and misalign teams around features rather than results. Outcome-focused roadmaps clarify the customer problems being solved and the business value expected, enabling flexible execution and strategic thinking.
Instructions
-
Gather Information: If the user provides a current roadmap, read it carefully. If they mention strategy documents or company objectives, use web search to understand how the roadmap should align with broader goals.
-
Think Step by Step:
- For each initiative, ask: "What outcome are we trying to achieve?"
- What customer problem are we solving?
- What business metric will improve?
- How will this impact the customer experience or business?
- Is there a better, different way to achieve the same outcome?
-
Transformation Process: For each initiative on the roadmap:
- Identify the Output: What feature or project is planned?
- Uncover the Outcome: Why are we building it? What changes for customers or business?
- Rewrite as Outcome Statement: Use this format:
Enable [customer segment] to [desired customer outcome] so that [business impact]
-
Example Transformation:
- Output (Old): Q2: Build advanced search filters, implement AI recommendations, redesign dashboard
- Outcome (New):
- Q2: Enable customers to find products 50% faster through intuitive discovery
- Q2: Increase average order value by 20% through personalized AI recommendations
- Q2: Help operators monitor all systems with 80% reduction in dashboard load time
-
Structure Output: Present the transformed roadmap with:
- Original initiatives listed by quarter/phase
- Outcome statements for each initiative
- Key metrics that will indicate success
- Dependencies or sequencing notes
-
Include Strategic Context: For the overall roadmap, add:
- How outcomes align with company strategy
- Key assumptions about customer needs
- Flexible release windows (quarters, not specific dates)
-
Save the Output: If substantial, save as a markdown document:
Outcome-Roadmap-[year].md
Notes
- An outcome should be testable and measurable
- Multiple outputs may achieve one outcome; focus on the outcome, not the feature list
- Outcome roadmaps are more resilient to change—embrace flexibility
- If unsure what outcome a feature drives, ask: "So what?" until you reach real customer/business value