AutoGineer
Generated banner for Outcome Roadmap
Generated logo for Outcome Roadmap

Outcome Roadmap

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill acts as a product management guide to help teams pivot from output-based roadmaps—which focus on specific features—to outcome-based roadmaps that emphasize strategic intent and measurable results. By analyzing existing initiatives and applying a structured 'so what?' inquiry process, the agent helps rewrite feature lists into clear, testable outcome statements. This approach fosters strategic alignment, encourages flexible execution, and ensures that development efforts are directly tied to customer problems and business value.

What it does

  • Analyzes existing feature-based roadmap initiatives.
  • Identifies the underlying customer problems and business objectives for each feature.
  • Rewrites initiatives into standardized outcome statements.
  • Maps outcomes to key success metrics and strategic goals.
  • Structures the roadmap into flexible time-based phases.
  • Provides guidance on aligning product work with broader company strategy.

When to use it

  • When transitioning a team from feature-factory delivery to outcome-driven product management.
  • When a roadmap feels disconnected from business goals or customer needs.
  • When you need to communicate strategic intent to stakeholders rather than just a list of features.
  • When you want to increase team flexibility by focusing on results instead of rigid feature deadlines.

Advantages

  • Increases strategic alignment across the organization.
  • Clarifies the 'why' behind product development efforts.
  • Enables more flexible and resilient planning.
  • Focuses team energy on measurable customer and business impact.

Usage examples

“Rewrite my Q3 roadmap which currently lists 'Add dark mode', 'Integrate Stripe', and 'Update API docs'.”
The agent will analyze these features and propose outcome statements such as 'Enable users to reduce eye strain during night use to increase session duration' and 'Enable seamless payment processing to reduce checkout abandonment by 15%'.
“How can I make my product roadmap more strategic?”
The agent will guide you through the process of identifying the customer problems and business metrics behind your current initiatives, helping you reframe them into outcome-focused statements.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/outcome-roadmap/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip outcome-roadmap.zip -d .agents/skills

Documentation by Pawel Huryn

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

  1. 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.

  2. 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?

  3. 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]

  4. 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

  5. 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

  6. 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)

  7. 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

Further Reading

Files

LICENSE

MIT License

Copyright (c) 2026 Pawel Huryn

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-execution/skills/outcome-roadmap · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download outcome-roadmap.zip