Outcome Roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
Install
npx skills add jeremybrasher/grokbot-skills --skill outcome-roadmapgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/outcome-roadmap ~/.claude/skills/outcome-roadmapPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Outcome Roadmap — from features to results Converts a feature-focused roadmap into an outcome-focused one. **Core principle:** Teams build features, but customers and businesses care about outcomes. An outcome roadmap communicates WHAT CHANGES, not what gets built. --- ## The transformation formula For every initiative on the roadmap, apply: ``` Enable [customer segment] to [desired customer outcome] so that [business impact] ``` Examples: | Output (old) | Outcome (new) | |---|---| | Q2: Build advanced search filters | Q2: Enable customers to find products 50% faster through intuitive discovery | | Q2: AI recommendations | Q2: Increase average order value 20% through personalised recommendations | | Q3: Dashboard redesign | Q3: Help operators monitor all systems with 80% less time spent on dashboards | | Q3: SSO integration | Q3: Remove auth friction for enterprise admins so we can close 3+ enterprise deals | | Q4: Mobile app | Q4: Enable users to complete core workflows on mobile so 7-day retention increases from 20% to 35% | --- ## How to apply ### Step 1 — Read the existing roadmap If the user provides a roadmap file, read it. If they describe it verbally, extract the initiative list. For each initiative, ask internally: - What feature / project is planned? - **Why** are we building it? What changes for customers or the business? - What metric will improve, and by how much? - Is there a better, different way to achieve the same outcome?
Details
- Skill name
outcome-roadmap- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/outcome-roadmap/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Outcome Roadmap skill do?
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
How do I install the Outcome Roadmap skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill outcome-roadmap. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Outcome Roadmap popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Paid Ads
38jeremybrasher/grokbot-skills
Coordinate safe, evidence-based paid-media work across Google Ads, Meta Ads, X Ads, LinkedIn Ads, TikTok, Amazon, and ChatGPT Ads. Use for broad ads questions, multi-channel strategy, budgets, CPA or ROAS, campaign requests, spend, ad performance, or when routing to the right NotFair paid-ads skill.
Opportunity Solution Tree
38jeremybrasher/grokbot-skills
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a PRD for a complex feature space.
Paid Ads Tiktok
38jeremybrasher/grokbot-skills
Plan and review TikTok Ads creative experiments with measurement, rights, and conversion guardrails. Use for TikTok advertising, Spark Ads, short-form video ads, creator briefs, TikTok campaign setup, or TikTok performance exports.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.