- AgentHub: 13 files updated with non-engineering examples (content drafts, research, strategy) — engineering stays primary, cross-domain secondary - AgentHub: 7 slash commands, 5 Python scripts, 3 references, 1 agent, dry_run.py validation (57 checks) - Marketplace: agenthub entry added with cross-domain keywords, engineering POWERFUL updated (25→30), product (12→13), counts synced across all configs - SEO: generate-docs.py now produces keyword-rich <title> tags and meta descriptions using SKILL.md frontmatter — "Claude Code Skills" in site_name propagates to all 276 HTML pages - SEO: per-domain title suffixes (Agent Skill for Codex & OpenClaw, etc.), slug-as-title cleanup, domain label stripping from titles - Broken links: 141→0 warnings — new rewrite_skill_internal_links() converts references/, scripts/, assets/ links to GitHub source URLs; skills/index.md phantom slugs fixed (6 marketing, 7 RA/QM) - Counts synced: 204 skills, 266 tools, 382 refs, 16 agents, 17 commands, 21 plugins — consistent across CLAUDE.md, README.md, docs/index.md, marketplace.json, getting-started.md, mkdocs.yml - Platform sync: Codex 163 skills, Gemini 246 items, OpenClaw compatible Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
3.1 KiB
3.1 KiB
title, description
| title | description |
|---|---|
| Roadmap Communicator — Agent Skill for Product Teams | Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers. Agent skill for Claude Code, Codex CLI, Gemini CLI, OpenClaw. |
Roadmap Communicator
:material-lightbulb-outline: Product
:material-identifier: `roadmap-communicator`
:material-github: Source
Install:
claude /plugin install product-skills
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.