Preparing roadmap narratives, release notes, changelogs

Roadmap communicator

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.

---
name: roadmap-communicator
description: Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.
---

# 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

Overview

Create clear roadmap communication artifacts for internal and external stakeholders.

What you get

Problem context
What changed
Why it matters
Who benefits most
How to get started
Call to action and feedback channel

Manual install (npx, ZIP)

Claude Codenpx skills add alirezarezvani/claude-skills --skill roadmap-communicator -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \
  | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/product-team/skills/roadmap-communicator

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/43ee29f0874397f55585/roadmap-communicator.zip" -OutFile "$env:TEMP\roadmap-communicator.zip"; Expand-Archive "$env:TEMP\roadmap-communicator.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.5 KB
references/2 files · 2.0 KB
scripts/1 file · 4.9 KB

Read the files here

alirezarezvani/19392f74 files

SKILL.md2.5 KB

SKILL.md

Show the full text93 lines

roadmap-communicator/SKILL.md93 lines · 2.5 KB

PreviewCode

Outline

RawView on GitHub

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.

1	---
2	name: roadmap-communicator
3	description: Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.
4	---
5
6	# Roadmap Communicator
7
8	Create clear roadmap communication artifacts for internal and external stakeholders.
9
10	## When To Use
11
12	Use this skill for:
13	- Building roadmap presentations in different formats
14	- Writing stakeholder updates (board, engineering, customers)
15	- Producing release notes (user-facing and internal)
16	- Generating changelogs from git history
17	- Structuring feature announcements
18
19	## Roadmap Formats
20
21	1. Now / Next / Later
22	- Best for uncertainty and strategic flexibility.
23	- Communicate direction without false precision.
24
25	2. Timeline roadmap
26	- Best for fixed-date commitments and launch coordination.
27	- Requires active risk and dependency management.
28
29	3. Theme-based roadmap
30	- Best for outcome-led planning and cross-team alignment.
31	- Groups initiatives by problem space or strategic objective.
32
33	See `references/roadmap-templates.md` for templates.
34
35	## Stakeholder Update Patterns
36
37	### Board / Executive
38	- Outcome and risk oriented
39	- Focus on progress against strategic goals
40	- Highlight trade-offs and required decisions
41
42	### Engineering
43	- Scope, dependencies, and sequencing clarity
44	- Status, blockers, and resourcing implications
45
46	### Customers
47	- Value narrative and timing window
48	- What is available now vs upcoming
49	- Clear expectation setting
50
51	See `references/communication-templates.md` for reusable templates.
52
53	## Release Notes Guidance
54
55	### User-Facing Release Notes
56	- Lead with user value, not internal implementation details.
57	- Group by workflows or user jobs.
58	- Include migration/behavior changes explicitly.
59
60	### Internal Release Notes
61	- Include technical details, operational impact, and known issues.
62	- Capture rollout plan, rollback criteria, and monitoring notes.
63
64	## Changelog Generation
65
66	Use:
67	```bash
68	python3 scripts/changelog_generator.py --from v1.0.0 --to HEAD
69	```
70
71	Features:
72	- Reads git log range
73	- Parses conventional commit prefixes
74	- Groups entries by type (`feat`, `fix`, `chore`, etc.)
75	- Outputs markdown or plain text
76
77	## Feature Announcement Framework
78
79	1. Problem context
80	2. What changed
81	3. Why it matters
82	4. Who benefits most
83	5. How to get started
84	6. Call to action and feedback channel
85
86	## Communication Quality Checklist
87
88	- [ ] Audience-specific framing is explicit.
89	- [ ] Outcomes and trade-offs are clear.
90	- [ ] Terminology is consistent across artifacts.
91	- [ ] Risks and dependencies are not hidden.
92	- [ ] Next actions and owners are specified.
93