Back to Details

roadmap-communicator

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Roadmap Communicator

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
使用此技能可完成以下工作：
  • 制作不同格式的路线图演示文稿
  • 撰写面向不同利益相关者的更新内容（董事会、工程团队、客户）
  • 生成发布说明（面向用户和内部使用）
  • 从git历史记录生成变更日志
  • 构建功能公告的结构

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.
  1. Now / Next / Later
  • 最适合存在不确定性且需要战略灵活性的场景。
  • 传达方向时避免虚假的精确性。
  1. Timeline roadmap
  • 最适合有固定日期承诺和发布协调的场景。
  • 需要主动进行风险和依赖关系管理。
  1. Theme-based roadmap
  • 最适合以成果为导向的规划和跨团队对齐。
  • 按问题领域或战略目标对举措进行分组。
可查看
references/roadmap-templates.md
获取模板。

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.
  • 价值阐述和时间窗口
  • 当前可用功能与即将推出功能的对比
  • 清晰设定预期
可查看
references/communication-templates.md
获取可复用模板。

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:
bash
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
使用方式：
bash
python3 scripts/changelog_generator.py --from v1.0.0 --to HEAD
功能特性：
  • 读取git日志范围
  • 解析conventional commit前缀
  • 按类型分组条目（
    feat
    , 
    fix
    , 
    chore
    等）
  • 输出markdown或纯文本格式

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
  1. 问题背景
  2. 变更内容
  3. 重要性说明
  4. 主要受益人群
  5. 入门指南
  6. 行动号召与反馈渠道

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.
  • 明确针对特定受众的表述方式。
  • 清晰说明成果和权衡事项。
  • 所有文档中的术语保持一致。
  • 不隐瞒风险和依赖关系。
  • 指定后续行动和负责人。