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:
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.