Agent skill · product strategy · borghei
roadmap-communicator
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.
Why this skill is useful
Adds 3 executable scripts for translating roadmaps into audience-specific formats that are not commonly found in public documentation.
What it needs
Requires python3 installed locally. About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
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 roadmapaudiencetranslator.py with target audience. 3. Review the audience-specific output; tune language. Workflow 2 — Apply confidence bands to commitments 1. List proposed roadmap items. 2. Run confidencebandgenerator.py with team velocity history + estimation context. 3. Adjust item commitments based on output (commit / aspire / explore). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/roadmap-communicator