Generates tailored roadmap narratives, release notes, changelogs, and stakeholder updates for various audiences such as executives, engineering teams, and customers. It structures feature announcements and converts git history into formatted changelogs using specific communication frameworks.
Quality gate: INCONCLUSIVE · better answers · measured 2026-10-24 Blind-judged against the bare model on 2 requests: average lift -4.5 points (specificity, structure, method, fit). won 1/2, lift -4.5, tokens ×141.01
Security scan: clean · 2026-10-24 · 4 files · ran in sandbox no network calls, shell tricks, credential access or instruction tampering found in its files.
Try asking
Say it in your own words; the assistant finds this recipe by itself. Examples:
“Lav et roadmap i 'Nu/Næste/Senere' format for vores næste kvartal, med fokus på sikkerhedsforbedringer.”
“Generér en changelog fra git-historikken siden sidste release til brug for vores interne team.”
“Skriv release notes til vores kunder, der forklarer de nye rapporteringsfunktioner og eventuelle ændringer i adfærd.”
“Draft a Now/Next/Later roadmap for the Q3 product cycle, focusing on the new billing engine.”
“Generate a changelog from the git history between v2.1.0 and HEAD for the internal engineering team.”
“Write release notes for the latest customer-facing update, emphasizing the new dashboard features and migration steps.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free
Do not use this skill for writing technical design documents, API specifications, or detailed engineering implementation plans, as it focuses on communication and narrative rather than technical architecture. It is not for general copywriting or marketing blog posts that do not relate to product roadmaps or releases.
Details
When it is the right choice
Use this skill when you need to draft or refine communication artifacts that explain product progress, upcoming features, or recent changes to specific audiences. It is ideal for creating Now/Next/Later roadmaps, writing user-facing release notes, or generating changelogs from commit history. It also handles structuring feature announcements to highlight value and impact.
The full recipe the assistant reads
Roadmap Communicator
Create clear roadmap communication artifacts for internal and external stakeholders.
When To Use
Use this skill for:
- Building roadmap presentations in different formats
- Writing stakeholder updates (board, engineering, customers)
- Producing release notes (user-facing and internal)
- Generating changelogs from git history
- Structuring feature announcements
Roadmap Formats
Now / Next / Later
Best for uncertainty and strategic flexibility.
Communicate direction without false precision.
Timeline roadmap
Best for fixed-date commitments and launch coordination.
Requires active risk and dependency management.
Theme-based roadmap
Best for outcome-led planning and cross-team alignment.
Groups initiatives by problem space or strategic objective.
See references/roadmap-templates.md for templates.
Stakeholder Update Patterns
Board / Executive
Outcome and risk oriented
Focus on progress against strategic goals
Highlight trade-offs and required decisions
Engineering
Scope, dependencies, and sequencing clarity
Status, blockers, and resourcing implications
Customers
Value narrative and timing window
What is available now vs upcoming
Clear expectation setting
See references/communication-templates.md for reusable templates.
Release Notes Guidance
User-Facing Release Notes
Lead with user value, not internal implementation details.
Group by workflows or user jobs.
Include migration/behavior changes explicitly.
Internal Release Notes
Include technical details, operational impact, and known issues.
Capture rollout plan, rollback criteria, and monitoring notes.
Changelog Generation
Use:
python3 scripts/changelog_generator.py --from v1.0.0 --to HEAD
Features:
- Reads git log range
- Parses conventional commit prefixes
- Groups entries by type (feat, fix, chore, etc.)
- Outputs markdown or plain text
Feature Announcement Framework
Problem context
What changed
Why it matters
Who benefits most
How to get started
Call to action and feedback channel
Communication Quality Checklist
[ ] Audience-specific framing is explicit.
[ ] Outcomes and trade-offs are clear.
[ ] Terminology is consistent across artifacts.
[ ] Risks and dependencies are not hidden.
[ ] Next actions and owners are specified.
Files in this skill (5)
LICENSE
SKILL.md
references/communication-templates.md
references/roadmap-templates.md
scripts/changelog_generator.py
Where it comes from
Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path product-team/skills/roadmap-communicator, licence MIT. The upstream licence file ships inside the skill.