agentleFS
DTiapanDTiapan/battery/.agents/skills/roadmap-communicator/SKILL.md

roadmap-communicator

Skill0 starsChanged 2 months agoMITView on GitHub

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

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create clear roadmap communication artifacts for internal and external stakeholders.

    line 8
  2. Distinctive:

    Use this skill for:

    line 12
  3. Distinctive:

    Call to action and feedback channel

    line 84

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.