New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Outcome-Focused Roadmap Rewriter

by avelikiy in avelikiy/great_cto

Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes.

MITAuto-check passedProduct & Project Management

Install Outcome-Focused Roadmap Rewriter

skills CLI
$ npx skills add avelikiy/great_cto --skill outcome-roadmap -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install avelikiy/great_cto outcome-roadmap --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/outcome-roadmap .claude/skills/outcome-roadmap && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
outcome-roadmap
GitHub stars
102
Token cost
~1.3k tokens
SKILL.md length
517 words
Files
1
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes.

  • Works in 5 steps: Read the existing roadmap → Rewrite each initiative as an outcome → Group by strategic theme (optional) → …
  • A roadmap lists features and not the results they should achieve
  • SKILL.md covers The transformation formula, How to apply, Anti-patterns and Integration with pm agent
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill converts an output-focused roadmap into an outcome-focused one. Each initiative is rewritten with a fixed formula: enable a customer segment to reach a desired outcome so that a business impact follows. A build-advanced-search-filters item, for instance, becomes a statement about customers finding products faster, ideally with a metric attached.

The agent reads the roadmap file or pulls initiatives out of your description, asks of each one why it is being built and which metric should move, and keeps asking so what until it reaches real customer or business value. Roadmaps with five or more items can be grouped into themes such as retention, acquisition, monetization and ops efficiency. The skill is limited to the Read and Write tools.

When your agent uses it

  • A roadmap lists features and not the results they should achieve
  • Making a roadmap more strategic before a leadership review
  • Explaining what success looks like next to what will be built

Example prompts

  • “Rewrite the roadmap in docs/roadmap.md as outcomes instead of features.”
  • “Turn the Q3 SSO integration item into an outcome statement with a metric.”
  • “Group these eight initiatives into themes and phrase each one as customer impact.”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Read the existing roadmap
  2. Rewrite each initiative as an outcome
  3. Group by strategic theme (optional)
  4. Output format
  5. Validate

What it can do on your machine

Read from SKILL.md and the folder at commit 97dd037. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Outcome-Focused Roadmap Rewriter loads about 1.3k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 517 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from avelikiy/great_cto at commit 97dd037, republished under its MIT licence (© avelikiy). 517 words, ~1,294 tokens.

Download SKILL.mdSave it as .claude/skills/outcome-roadmap/SKILL.md (or your agent's skills folder).
name
outcome-roadmap
description
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.
allowed-tools
Read, Write
when_to_use
Apply when: - CTO provides a feature list and asks "what should we do next quarter" - pm agent receives a roadmap full of features, not outcomes…
effort
low
paths
docs/plans/**, docs/requirements/**

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 filtersQ2: Enable customers to find products 50% faster through intuitive discovery
Q2: AI recommendationsQ2: Increase average order value 20% through personalised recommendations
Q3: Dashboard redesignQ3: Help operators monitor all systems with 80% less time spent on dashboards
Q3: SSO integrationQ3: Remove auth friction for enterprise admins so we can close 3+ enterprise deals
Q4: Mobile appQ4: 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?
Step 2 — Rewrite each initiative as an outcome

For each item in the roadmap:

  1. Identify the output: What feature or project is planned?
  2. Uncover the outcome: Why are we building it? Keep asking "So what?" until you reach real customer or business value.
  3. Rewrite: Use the formula above. Include a metric if possible.

"So what?" chain example:

  • "We're adding search filters" → So what?
  • "Users can narrow results" → So what?
  • "Users find what they're looking for faster" → So what?
  • "Users convert at higher rates because they find products before abandoning" ✅ That's the outcome.
Show full SKILL.md (222 more words)Show less
Step 3 — Group by strategic theme (optional)

If the roadmap has 5+ items, group related outcomes into themes:

  • Retention (outcomes that reduce churn)
  • Acquisition (outcomes that improve conversion)
  • Monetisation (outcomes that increase revenue per user)
  • Ops efficiency (outcomes that reduce internal cost/time)
Step 4 — Output format
markdown
## Outcome Roadmap — <Product> <Quarter/Year>

### Strategic context
<1–2 sentences on what the team is optimising for this period>

### Q<N> Outcomes

| Initiative | Outcome Statement | Primary Metric | Target |
|------------|------------------|----------------|--------|
| <original feature name> | Enable [segment] to [outcome] so that [business impact] | <metric> | <target> |

### What we're NOT doing this quarter (and why)
- <deprioritised initiative>: <reason — not enough signal / too early / wrong priority>

### Key assumptions
- <assumption this roadmap depends on — if it's wrong, the outcomes change>
Step 5 — Validate

Before presenting, check:

  • Every outcome has a measurable component (%, number, ratio, frequency)
  • "So what?" has been applied to every item — no pure feature descriptions remain
  • At least one "Not doing" item is stated — otherwise scope is unbounded
  • Outcomes align with stated OKRs or strategic goals in PROJECT.md

Anti-patterns

❌ "We will build X" — that's an output, not an outcome.

❌ "Improve UX" — unmeasurable. Rewrite as: "Reduce time to complete checkout from 4min to 90sec".

❌ Outcome without a metric — if you can't measure it, you can't know if you achieved it.

❌ Outcomes that require building a specific solution — "Enable users to access features via mobile app" locks the solution. Better: "Enable users to complete core workflows on any device".

Integration with pm agent

When the pm agent receives a feature list without a PRD:

  1. Check if the list looks like outputs (feature names) or outcomes (result statements)
  2. If outputs → apply this skill to transform before decomposing into tasks
  3. Pass the outcome statements into the PLAN doc as the "Why" for each task group

© avelikiy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/outcome-roadmap of avelikiy/great_cto.

Open the folder on GitHubat commit 97dd037

Compare with similar skills

Outcome-Focused Roadmap Rewriter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Outcome-Focused Roadmap Rewriter compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Outcome-Focused Roadmap Rewriter this skillavelikiy/great_cto102—~1.3kAutomated safety check: PassMIT
Product Strategistalirezarezvani/claude-skills28k2 repos~1.8kAutomated safety check: PassMIT
AI Product Strategy InterviewerPrepLabsAI/InterviewMentor112—~4.5kAutomated safety check: PassMIT
Product PlannerBuildGreatProducts/builder-os228—~4.6kAutomated safety check: PassMIT
End-to-End Product Strategy Sessiondeanpeters/Product-Manager-Skills7.2k1 repos~4.2kAutomated safety check: PassCustom licence
Build MvpBuildGreatProducts/builder-os228—~1.2kAutomated safety check: NotesMIT

Similar skills

  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Product & Project ManagementAuto-check passed

  • AI Product Strategy Interviewer

    PrepLabsAI/InterviewMentor

    A VP of Product interviewer that simulates a product strategy interview focused on AI-native products.

    112 GitHub stars~4.5k tokensUpdated 4 days ago
    Product & Project ManagementAuto-check passed

  • Product Planner

    BuildGreatProducts/builder-os

    Vision intake conversation followed by generation of three product documents — docs/product-vision.md (strategy and brand), docs/prd.md (technical spec for coding agents), and…

    228 GitHub stars~4.6k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check passed

  • End-to-End Product Strategy Session

    deanpeters/Product-Manager-Skills

    Orchestrates positioning, problem discovery, solution exploration, and roadmap planning into one multi-week strategy process.

    7.2k GitHub starsUsed in 1 repo~4.2k tokens
    Product & Project ManagementAuto-check passed

  • Build Mvp

    BuildGreatProducts/builder-os

    Use inside a product repository when the user wants the full MVP built from their BuilderOS spec documents.

    228 GitHub stars~1.2k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check: notes

  • Outcome Roadmap

    borghei/Claude-Skills

    Transform output-based feature lists into outcome-driven Now/Next/Later roadmaps using the "so what?" technique.

    891 GitHub stars~1.4k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

More from avelikiy/great_cto

All 27 skills in this repo

  • AnyDesign Design Analyzer

    avelikiy/great_cto

    Analyzes a screenshot, website or Figma file and writes a `design.md` with its token system, component inventory and reconstruction notes, or an `element.md` for one element.

    102 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed

  • Opportunity Solution Tree

    avelikiy/great_cto

    Builds an Opportunity Solution Tree that links one measurable outcome to customer opportunities, candidate solutions and experiments.

    102 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Exposed Secret Rotation

    avelikiy/great_cto

    Turns a leaked key, token or password into one tracked rotation task the moment it's spotted, instead of a reminder repeated every session.

    102 GitHub stars~884 tokensUpdated yesterday
    Auto-check: notes

  • Skeptical Triage

    avelikiy/great_cto

    Runs a three-round self-challenge plus an arbiter over high-stakes findings, so false positives from reviews, audits and flaky-test verdicts do not become blockers.

    102 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check: notes

  • Aesthetic Instrument

    avelikiy/great_cto

    greatcto's own committed aesthetic — the instrument panel. An agent skill from avelikiy/great_cto.

    102 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Anti Patterns

    avelikiy/great_cto

    Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems.

    102 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Outcome-Focused Roadmap Rewriter

What does Outcome-Focused Roadmap Rewriter do?

Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes. This skill converts an output-focused roadmap into an outcome-focused one. Each initiative is rewritten with a fixed formula: enable a customer segment to reach a desired outcome so that a business impact follows.

When should I use Outcome-Focused Roadmap Rewriter?

Outcome-Focused Roadmap Rewriter fits situations like: A roadmap lists features and not the results they should achieve; making a roadmap more strategic before a leadership review; explaining what success looks like next to what will be built.

How do I install Outcome-Focused Roadmap Rewriter in Claude Code?

Run `npx skills add avelikiy/great_cto --skill outcome-roadmap -a claude-code`. Or copy the skill folder (skills/outcome-roadmap in avelikiy/great_cto) into .claude/skills/outcome-roadmap in your project. Claude Code loads it when a task matches its description.

How do I install Outcome-Focused Roadmap Rewriter in Codex?

Run `npx skills add avelikiy/great_cto --skill outcome-roadmap -a codex`. Or copy the skill folder (skills/outcome-roadmap in avelikiy/great_cto) into .agents/skills/outcome-roadmap in your project. Codex loads it when a task matches its description.

Can I use Outcome-Focused Roadmap Rewriter in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avelikiy/great_cto --skill outcome-roadmap -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/outcome-roadmap, .gemini/skills/outcome-roadmap, .github/skills/outcome-roadmap and .opencode/skills/outcome-roadmap in your project.

What does Outcome-Focused Roadmap Rewriter need to run?

SKILL.md names no scripts, command-line tools or credentials: Outcome-Focused Roadmap Rewriter is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write.

Does Outcome-Focused Roadmap Rewriter access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Outcome-Focused Roadmap Rewriter safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Outcome-Focused Roadmap Rewriter use?

Outcome-Focused Roadmap Rewriter is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Outcome-Focused Roadmap Rewriter use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Outcome-Focused Roadmap Rewriter?

Skills that share tags, products or a category with Outcome-Focused Roadmap Rewriter: Product Strategist (alirezarezvani/claude-skills, 28k stars), AI Product Strategy Interviewer (PrepLabsAI/InterviewMentor, 112 stars), Product Planner (BuildGreatProducts/builder-os, 228 stars) and End-to-End Product Strategy Session (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Outcome-Focused Roadmap Rewriter?

avelikiy (a GitHub user) maintains it in avelikiy/great_cto, which has 102 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 9, 2026.

Source: avelikiy/great_cto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.