Agent skill · product strategy · borghei
roadmap-communication
Same roadmap, three audiences. Produce executive, customer, and internal roadmap variants with audience-appropriate framing, detail, and risk language. Use for quarterly roadmap publication, board packets, and customer/sales roadmaps.
Why this skill is useful
Provides structured templates and guidelines for creating tailored roadmap variants that align with different audience needs, which the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Roadmap Communication Expert Overview A single roadmap cannot serve every audience. Executives need confidence and strategic framing. Customers need plausible promises with credible timelines. Internal teams need detail, dependency awareness, and honest risk. When PMs publish one roadmap to all three, one audience is always wrong -- either the executives are bored, customers feel misled, or engineers feel managed. This skill produces three variants of the same underlying roadmap, each tailored to its audience. The underlying source of truth -- the roadmap data -- stays single; the framing, level of detail, risk language, and visualization all change. The variants share names and identifiers so a customer reference can be traced back through the internal variant to the actual ticket. The structural backbone is Now / Next / Later (Janna Bastow, ProdPad), which Marty Cagan calls "right-sizing the roadmap" -- forecast confidence decreases with time horizon, so commit explicitly to "Now," name "Next" by theme, and keep "Later" deliberately fuzzy. Core Capabilities Three audience variants — executive (outcome-led, confidence-rated, 1 page), customer (theme-led, benefit-framed, no firm dates), and internal (feature-led with owners, dependencies, and explicit risk). Now / Next / Later right-sizing — encode the confidence gradient and calibrate it per audience. Outcome-vs-feature framing — translate features into customer outcomes for the executive and customer variants. Triangulation check — trace one Now item across all three variants to guarantee consistent identity and framing. When to Use Quarterly roadmap publication -- the regular cadence where you communicate to multiple audiences. Pre-board meeting -- the executive variant feeds the board packet. Annual customer conference -- the customer variant becomes the conference roadmap session. Engineering kickoff -- the internal variant grounds sprint planning across multiple teams. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/roadmap-communication