communicate-roadmap

Convert technical roadmap content into a user-focused external roadmap document.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/alexmensch/claude-sdlc-plugins --skill communicate-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: communicate-roadmap
Source: https://github.com/alexmensch/claude-sdlc-plugins/tree/main/plugins/roadmap/skills/communicate-roadmap
Command: npx skills add https://github.com/alexmensch/claude-sdlc-plugins --skill communicate-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a technical, developer-oriented ROADMAP.md into a short, clear external roadmap that speaks to users about outcomes and benefits rather than implementation details. It removes internal jargon and reframes releases as user-facing improvements so recipients understand what will change for them and why it matters.

Core Features & Use Cases

  • Load and interpret planning artifacts: Reads product/ROADMAP.md and extracts the Overview, Target Users, planned releases, feature lists, and sequencing rationale.
  • Translate technical details into user benefits: Reframes release names and feature intents as user-centered headlines and outcome statements that answer "so what?".
  • Collaborative drafting workflow: Asks one focused question about audience and goal, presents a full draft for approval, accepts revision requests, and repeats until approved.
  • Save publishable output: After approval, writes a concise external roadmap to product/EXTERNAL-ROADMAP.md and reports the tone and emphasis used.
  • Use case: Prepare an announcement for existing customers that sets expectations for upcoming releases and highlights the concrete improvements they will experience.

Quick Start

Use communicate-roadmap to draft an external roadmap from product/ROADMAP.md that reframes upcoming releases as user benefits and save it to product/EXTERNAL-ROADMAP.md.

Frequently Asked Questions about communicate-roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a technical product roadmap into user-facing release announcements?

An external roadmap translates technical feature lists into user-centered outcome statements that set customer expectations. It reframes developer-oriented milestones as concrete benefits, removing internal jargon so recipients understand upcoming improvements without needing implementation context.

How do I draft an external roadmap from a ROADMAP.md file?

To draft an external roadmap from a ROADMAP.md file, load the planning artifacts, extract the overview and target users, and translate release sequencing into user-focused headlines. The workflow asks one audience question, generates a draft, iterates on revisions, and saves the approved output to a separate external file.

What is the best way to communicate planned releases to existing customers?

The best way to communicate planned releases to existing customers is to publish a directional external roadmap document. This highlights concrete improvements and sets expectations by focusing on user benefits rather than internal implementation details or sequencing rationale.

Do I need feature requirement files to generate a customer-facing roadmap?

Yes, you need a product/ROADMAP.md and associated feature requirement files to generate a customer-facing roadmap. These planning artifacts provide the source material needed to extract planned releases and reframe technical feature intents into user-facing outcome statements.

Can I iteratively revise a generated external roadmap before saving it?

Yes, you can iteratively revise a generated external roadmap before saving it. The drafting workflow presents a full draft for approval, accepts revision requests based on your audience needs, and repeats this cycle until you approve the content for final output.