How to use the Outcome Roadmap Rewriter agent skill

What is an agent skill and what does this one do?

An agent skill is a packaged set of instructions that an AI agent loads when a request matches the skill's purpose. This one is defined in a single file, SKILL.md, which tells the agent to act as an experienced product manager helping you shift from output-focused roadmaps to outcome-focused roadmaps.

Output-focused roadmaps list features and projects. Outcome-focused roadmaps describe the customer problem being solved and the business value expected. The skill works through each initiative and asks what outcome you are trying to achieve, what customer problem is being solved, and which business metric should improve.

• Identifies the output (the feature or project) for each initiative
• Uncovers the outcome by asking what changes for customers or the business
• Rewrites each item in the format: Enable [customer segment] to [desired customer outcome] so that [business impact]
• Presents the result by quarter, with success metrics, dependencies or sequencing notes, and strategic context
• May use web search to align the roadmap with company strategy when you mention strategy documents or objectives
• Saves a markdown document named Outcome-Roadmap-[year].md if the output is substantial

Install the outcome-roadmap skill

Download the ZIP file for the outcome-roadmap skill from this directory page. Unzip it so that the outcome-roadmap folder, containing SKILL.md, sits inside one of these locations:

• Personal skills folder: ~/.claude/skills/ (available across your projects)
• Project skills folder: .claude/skills/ inside your project (available only to that project)
• Claude apps: upload the ZIP under Settings → Capabilities → Skills

How do you trigger the skill with a natural request?

You do not need a special command. Describe what you want in plain language, and the agent will load the skill when your request matches its description. The skill's description covers shifting to outcome roadmaps, making a roadmap more strategic, and rewriting feature lists as outcomes.

Paste your current roadmap into the conversation, or point the agent to a file that contains it. Mention any strategy document or company objectives you want the roadmap to align with, since the skill uses those to add strategic context.

• "Rewrite this feature roadmap as outcomes, grouped by quarter."
• "Make this roadmap more strategic for our leadership review."
• "Turn these feature requests into outcome statements with success metrics."
• "We are moving to outcome roadmaps. Here is our Q1 to Q4 plan. Help me rewrite it."

What does a good result look like?

The skill's own example turns a line of features into outcome statements tied to a quarter. For instance, a Q2 item to build advanced search filters becomes a statement that enables customers to find products faster through intuitive discovery. Each statement should be testable and measurable.

Review every metric the agent proposes. The skill itself notes that a feature may be linked to a single outcome or several, and that the agent may invent plausible-sounding metrics when business goals or customer data are unknown. Replace or validate any figure with data your team actually has.

What do you need before you start?

The skill lists no required tools or packages. Its main input is your existing roadmap. The more context you provide, the better the result, because the skill asks what customer problem each initiative solves and which metric should move.

Have ready: your current roadmap, the business goals it should support, and any customer data or research you have. Without these, the outcomes and metrics will be guesses that your team needs to check.

• Your current roadmap listing features and projects by quarter or phase
• Company strategy or objectives, if you want alignment checked
• Customer data or research, so metrics are grounded

Safety notes: scripts and network access

According to the skill's listing, it does not run scripts. It does use the network, because it may run web searches to align the roadmap with company strategy. Be aware of this if you work with confidential strategy documents, and decide what you are comfortable sharing with the agent before you start.

The skill saves its output as a local markdown file only when the result is substantial, so check where the file is written in your environment before sharing it.

• Runs scripts: no
• Uses network: yes (web search for strategy alignment)
• Requires: nothing listed

Tips for better outcome roadmaps

Keep the quarter-level windows the skill recommends. Outcome roadmaps are meant to be flexible, so avoid forcing specific delivery dates onto them. If your team needs a detailed delivery schedule, this skill is not the right tool for that part of the plan.

When an outcome is unclear, keep asking "So what?" until you reach real customer or business value. Treat the output as a draft for discussion, not a finished plan.

• Give the agent your real business goals and customer data
• Ask "So what?" about any outcome that sounds vague
• Use the skill's Further Reading links on vision, OKRs and outcome types to deepen the framework