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

Roadmap Communicator

by borghei in borghei/Claude-Skills

Translate one internal roadmap into audience-appropriate formats with confidence-band discipline.

MITAuto-check passedProduct & Project Management

Install Roadmap Communicator

skills CLI
$ npx skills add borghei/Claude-Skills --skill roadmap-communicator -a claude-code

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

GitHub CLI
$ gh skill install borghei/Claude-Skills roadmap-communicator --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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/product-team/roadmap-communicator .claude/skills/roadmap-communicator && 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
roadmap-communicator
GitHub stars
881
Token cost
~1.9k tokens
SKILL.md length
798 words
Files
7 (incl. scripts, references)
Skills in repo
349
Repo updated
First seen
Licence
MIT

At a glance

Translate one internal roadmap into audience-appropriate formats with confidence-band discipline.

  • Works in 3 steps: Capture the master roadmap with… → Run roadmap_audience_translator.py with… → Review the audience-specific output;…
  • Preparing a roadmap readout
  • SKILL.md covers When to use this skill, Inputs the advisor expects, Clarify First and Workflows, plus 5 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Roadmap Communicator is an agent skill from borghei/Claude-Skills. Translate one internal roadmap into audience-appropriate formats with confidence-band discipline. Use when preparing a roadmap readout, tailoring it for an exec, customer, eng, or sales audience, or auditing over-promise risk.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/audience-specific-formats.md`, `references/now-next-later-and-themes.md` and `references/roadmap-communication-patterns.md`).

It sits in Product & Project Management, covering Product roadmapping. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Preparing a roadmap readout
  • Tailoring it for an exec
  • Auditing over-promise risk

Example prompts

  • “/roadmap-communicator”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Capture the master roadmap with confidence bands.
  2. Run roadmap_audience_translator.py with target audience.
  3. Review the audience-specific output; tune language.

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    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

Roadmap Communicator loads about 1.9k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 798 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.4k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 798 words, ~1,886 tokens.

Download SKILL.mdSave it as .claude/skills/roadmap-communicator/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
roadmap-communicator
description
Translate one internal roadmap into audience-appropriate formats with confidence-band discipline. Use when preparing a roadmap readout, tailoring it for an exec, customer, eng, or sales audience, or auditing over-promise risk.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
product-team
metadata.domain
roadmap
metadata.updated
2026-05-27
metadata.tags
roadmap, communication, prd, now-next-later, themes, board, customer

Roadmap Communicator

A skill focused on communicating the roadmap — different audiences need different formats and confidence levels. Distinct from product-strategist (which builds the strategy) and agile-product-owner (which manages sprint execution).

When to use this skill

  • Preparing a roadmap readout for execs, board, customers, or sales
  • Translating a single internal roadmap to multiple audience formats
  • Auditing roadmap commitments for over-promise risk
  • Building a now-next-later view of priorities
  • Communicating roadmap changes to stakeholders
  • Preparing a what-changed/what's-next memo

Inputs the advisor expects

  • The internal roadmap (themes, initiatives, target dates, confidence)
  • Target audience(s) for the communication
  • Recent roadmap changes (added, removed, slipped)
  • Cross-functional commitments (engineering, sales, marketing)

Clarify First

Before generating the roadmap communication, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Target audience — board/exec, customer, sales, or engineering (selects the audience-format matrix row and granularity)
  • Confidence band per item — commit, plan, aspire, or strategic intent (drives the language and over-promise guardrails)
  • Recent changes — what was added, removed, or slipped since the last readout (drives the what-changed diff memo)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Workflows

Workflow 1 — Translate roadmap for a specific audience
  1. Capture the master roadmap with confidence bands.
  2. Run roadmap_audience_translator.py with target audience.
  3. Review the audience-specific output; tune language.
bash
python3 roadmap-communicator/scripts/roadmap_audience_translator.py \
  --input roadmap.json --audience customer --format markdown
Workflow 2 — Apply confidence bands to commitments
  1. List proposed roadmap items.
  2. Run confidence_band_generator.py with team velocity history + estimation context.
  3. Adjust item commitments based on output (commit / aspire / explore).
bash
python3 roadmap-communicator/scripts/confidence_band_generator.py \
  --input items.json --format markdown
Workflow 3 — Generate a roadmap diff report
  1. Capture previous roadmap snapshot + current roadmap.
  2. Run roadmap_diff_reporter.py to produce what-changed memo.
bash
python3 roadmap-communicator/scripts/roadmap_diff_reporter.py \
  --previous roadmap_q1.json --current roadmap_q2.json --format markdown

Decision frameworks

Audience-format matrix
AudienceRight formatWrong format
Board / execThemes + bets + KPIs (1 page)Feature list
Customers / publicWhat's new + what's next (themes; no dates)Internal commit list
SalesThemes + competitive positioning + customer-ask coverageEngineering jargon
EngineeringThemes + quarter commitments + scoped detailVague aspirations
Internal companyThemes + progress + asksConfidential strategy
Partner / integratorAPI-relevant changes + breaking-change calendarAll-up roadmap

Same roadmap; different formats. Don't send the engineering commit list to customers.

Confidence bands

Apply per item:

BandLanguageAudience expectation
Commit"Will ship" with target dateHold us to this
Plan"Plan to ship" with target windowConfident but conditional
Aspire"Investigating" / "Exploring"Don't depend on this
Strategic intent"We believe X matters"Direction, not deliverable

Common errors:

  • Treating "plan" as "commit" — sets up disappointment
  • Communicating "commit" as "plan" — under-delivers excitement
  • No confidence band — every line read as commit
Now-next-later structure

A useful skeleton across audiences:

  • Now (in progress, < 1 quarter): commit-level items
  • Next (1-2 quarters out): plan-level items
  • Later (2-4 quarters): aspire-level items
  • Strategic intent (>4 quarters): direction only

This protects confidence: the closer in time, the firmer the commitment.

Show full SKILL.md (334 more words)Show less
Themes vs features

Communicate at the right granularity:

  • External / strategic: themes ("better collaboration")
  • Customer-specific: outcomes ("you'll be able to X")
  • Internal: features + tickets

Telling a customer "we're adding X in Q3" makes a commitment that may not be precise enough. Telling the team "we're going to improve collaboration somehow" is too vague.

Common engagements

"Help me write the customer roadmap section"
  1. Start with what they care about (outcomes, not features).
  2. Use themes + outcomes; avoid specific dates beyond the current quarter.
  3. Group: launching soon, in development, exploring.
  4. Avoid: features that depend on uncertain technical bets.
  5. Always include a "we'd love your input" hook.
"Help me prep the board roadmap section"
  1. Start with strategic themes (3-5).
  2. For each theme: what's shipped, what's coming, what's the bet.
  3. Tie to business outcomes (NRR impact, new revenue, cost saving).
  4. Surface 1-2 strategic risks transparently.
  5. End with 2-3 specific asks.
"Our customer is asking 'when will X ship?'"
  1. First check: is X actually committed? (Probably plan or aspire.)
  2. If commit: give a target window with caveats.
  3. If plan: "We're planning to ship in [window]; we'll know more by [date]."
  4. If aspire: "We're exploring; not in our committed roadmap."
  5. Document the customer asks; feed them back into prioritization.

Anti-patterns to avoid

  • One-size-fits-all roadmap. Different audiences get over- or under-served.
  • Date-only roadmap. Dates without confidence bands set up over-promise.
  • Public commitments engineering didn't sign off on. Trust breaks.
  • Roadmap that never changes. Reality changes; roadmap must.
  • Roadmap silence between updates. Customers / sales speculate.
  • Hiding strategic risks. Boards prefer honest risks over surprise misses.
  • Big bang annual roadmap with no quarterly delta. Misses change cycles.
  • Feature names instead of outcomes. "Notifications v2" tells the customer nothing.

References

  • references/roadmap-communication-patterns.md — format catalog + when to use
  • references/audience-specific-formats.md — per-audience templates
  • references/now-next-later-and-themes.md — structural patterns
  • product-team/product-strategist — strategy upstream of roadmap
  • product-team/agile-product-owner — sprint-level execution
  • product-team/product-manager-toolkit — broader PM tooling
  • c-level-advisor/cpo-advisor — CPO partnership
  • c-level-advisor/ceo-advisor — CEO / board alignment
  • business-growth/customer-success-manager — customer comms
  • marketing/ skills — external messaging alignment

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

Files

SKILL.md and 6 other files (scripts, references) in product-team/roadmap-communicator of borghei/Claude-Skills.

  • SKILL.md
  • references/audience-specific-formats.md
  • references/now-next-later-and-themes.md
  • references/roadmap-communication-patterns.md
  • scripts/confidence_band_generator.py
  • scripts/roadmap_audience_translator.py
  • scripts/roadmap_diff_reporter.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

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

Roadmap Communicator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Roadmap Communicator this skillborghei/Claude-Skills881—~1.9kAutomated safety check: PassMIT
Product Strategistalirezarezvani/claude-skills28k2 repos~1.8kAutomated safety check: PassMIT
Strategic Roadmap Planningdeanpeters/Product-Manager-Skills7.2k2 repos~4.7kAutomated safety check: PassCustom licence
Walking Skeleton Roadmap Scopingprime-radiant-inc/iterative-development181—~1.7kAutomated safety check: PassApache-2.0
AI Product Strategy InterviewerPrepLabsAI/InterviewMentor112—~4.5kAutomated safety check: PassMIT
Product PlannerBuildGreatProducts/builder-os227—~4.6kAutomated safety check: PassMIT

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

  • Strategic Roadmap Planning

    deanpeters/Product-Manager-Skills

    Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.

    7.2k GitHub starsUsed in 2 repos~4.7k tokens
    Product & Project ManagementAuto-check passed

  • Walking Skeleton Roadmap Scoping

    prime-radiant-inc/iterative-development

    Turns extracted requirements into a roadmap by choosing a walking skeleton iteration with its first journey scenario and ordering the remaining work into follow-on iterations.

    181 GitHub stars~1.7k tokensUpdated 4 mo ago
    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 yesterday
    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…

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

  • Outcome-Focused Roadmap Rewriter

    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.

    103 GitHub stars~1.3k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from borghei/Claude-Skills

All 349 skills in this repo

  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    881 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    881 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    881 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    881 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Roadmap Communicator

What does Roadmap Communicator do?

Translate one internal roadmap into audience-appropriate formats with confidence-band discipline. Roadmap Communicator is an agent skill from borghei/Claude-Skills. Translate one internal roadmap into audience-appropriate formats with confidence-band discipline.

When should I use Roadmap Communicator?

Roadmap Communicator fits situations like: preparing a roadmap readout; tailoring it for an exec; auditing over-promise risk.

How do I install Roadmap Communicator in Claude Code?

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

How do I install Roadmap Communicator in Codex?

Run `npx skills add borghei/Claude-Skills --skill roadmap-communicator -a codex`. Or copy the skill folder (product-team/roadmap-communicator in borghei/Claude-Skills) into .agents/skills/roadmap-communicator in your project. Codex loads it when a task matches its description.

Can I use Roadmap Communicator 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 borghei/Claude-Skills --skill roadmap-communicator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/roadmap-communicator, .gemini/skills/roadmap-communicator, .github/skills/roadmap-communicator and .opencode/skills/roadmap-communicator in your project.

What does Roadmap Communicator need to run?

Going by SKILL.md and its folder, Roadmap Communicator needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Roadmap Communicator 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 Roadmap Communicator 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Roadmap Communicator use?

Roadmap Communicator is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Roadmap Communicator use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.

What are the alternatives to Roadmap Communicator?

Skills that share tags, products or a category with Roadmap Communicator: Product Strategist (alirezarezvani/claude-skills, 28k stars), Strategic Roadmap Planning (deanpeters/Product-Manager-Skills, 7.2k stars), Walking Skeleton Roadmap Scoping (prime-radiant-inc/iterative-development, 181 stars) and AI Product Strategy Interviewer (PrepLabsAI/InterviewMentor, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Roadmap Communicator?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.

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