roadmap-communicator

name	roadmap-communicator
description	Manage — Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.
executor	HYBRID
skill_id	business.product-team.roadmap-communicator
status	ADOPTED
security	{"level":"standard","pii":false,"approval_required":false}
anchors	["business","customer_success","management","observability"]
tier	2
input_schema	[{"name":"code_or_task","type":"string","description":"Code snippet, script, or task description to process","required":true}]
output_schema	[{"name":"plan","type":"string","description":"Strategic plan or design document"},{"name":"next_steps","type":"array","description":"List of recommended next steps"}]

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.

2. Timeline roadmap

• Best for fixed-date commitments and launch coordination.
• Requires active risk and dependency management.

3. 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, , , etc.)