Roadmap communicator

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

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/roadmap-communicator.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/product-team/skills/roadmap-communicator#main ~/.claude/skills/roadmap-communicator

For one project only, change the path to .claude/skills/roadmap-communicator.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Roadmap communicator

Show the full text93 lines
namedescription
roadmap-communicatorUse 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

Roadmap Formats

  1. Now / Next / Later
  • Best for uncertainty and strategic flexibility.
  • Communicate direction without false precision.
  1. Timeline roadmap
  • Best for fixed-date commitments and launch coordination.
  • Requires active risk and dependency management.
  1. 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

  1. Problem context
  2. What changed
  3. Why it matters
  4. Who benefits most
  5. How to get started
  6. 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---
2name: roadmap-communicator
3description: Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.
4---
5 
6# Roadmap Communicator
7 
8Create clear roadmap communication artifacts for internal and external stakeholders.
9 
10## When To Use
11 
12Use 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 
211. Now / Next / Later
22- Best for uncertainty and strategic flexibility.
23- Communicate direction without false precision.
24 
252. Timeline roadmap
26- Best for fixed-date commitments and launch coordination.
27- Requires active risk and dependency management.
28 
293. Theme-based roadmap
30- Best for outcome-led planning and cross-team alignment.
31- Groups initiatives by problem space or strategic objective.
32 
33See `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 
51See `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 
66Use:
67```bash
68python3 scripts/changelog_generator.py --from v1.0.0 --to HEAD
69```
70 
71Features:
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 
791. Problem context
802. What changed
813. Why it matters
824. Who benefits most
835. How to get started
846. 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 

Discussion

Alternatives

Also in Roadmap & prioritiesSee all 277 in Product →