outcome-roadmap

Convert feature-focused roadmaps into outcome statements with metrics and strategic themes.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jeremybrasher/grokbot-skills --skill outcome-roadmap-jeremybrasher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: outcome-roadmap
Source: https://github.com/jeremybrasher/grokbot-skills/tree/main/collections/great-cto/skills/outcome-roadmap
Command: npx skills add https://github.com/jeremybrasher/grokbot-skills --skill outcome-roadmap-jeremybrasher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product roadmaps often list features to build rather than the results they should achieve, leaving stakeholders unclear on why work matters and how success will be measured. This Skill rewrites output-focused initiatives as measurable outcome statements tied to customer and business impact. ## Core Features & Use Cases - Outcome Transformation: Applies the formula "Enable [segment] to [outcome] so that [business impact]" to every roadmap initiative, using a "So what?" chain to uncover real value. - Strategic Grouping: Clusters five or more items into themes like Retention, Acquisition, Monetisation, and Ops efficiency. - Structured Output: Produces a roadmap table with outcome statements, primary metrics, targets, deprioritised items, and key assumptions. - Use Case: A CTO hands over a Q3 plan listing "SSO integration, dashboard redesign, mobile app." The Skill rewrites each as a measurable outcome, such as removing auth friction to close three or more enterprise deals. ## Quick Start Rewrite this feature-based roadmap as an outcome-focused roadmap with metrics and targets for each initiative.

Frequently Asked Questions about outcome-roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a feature roadmap into an outcome roadmap?▼

Apply the formula "Enable [customer segment] to [desired outcome] so that [business impact]" to each initiative. Use a "So what?" chain to move from the feature to real customer value, then attach a measurable metric and target.

What is the difference between output and outcome in a roadmap?▼

An output is what gets built, such as "advanced search filters." An outcome is the change it creates, such as "customers find products 50% faster." Outcome roadmaps communicate results and metrics rather than feature lists.

When should I not use an outcome roadmap transformation?▼

Skip it when the input already states outcomes with metrics, or when working on a single-feature PRD, which belongs in a dedicated PRD workflow instead. It is designed for multi-initiative roadmaps listing features.

How do I make roadmap outcomes measurable?▼

Attach a percentage, number, ratio, or frequency to every outcome, such as reducing checkout time from 4 minutes to 90 seconds. Avoid vague phrases like "improve UX" that cannot be verified.

Why does my outcome statement still lock in a solution?▼

Statements like "enable users to access features via mobile app" prescribe a solution rather than an outcome. Rewrite as the underlying result, such as "enable users to complete core workflows on any device," keeping solution options open.