Roadmap Communicator Skill for Claude

Roadmap Communicator

A skill focused on communicating the roadmap — different audiences

need different formats and confidence levels. Distinct from product-strategist

(which builds the strategy) and agile-product-owner (which manages sprint

execution).

When to use this skill

• Preparing a roadmap readout for execs, board, customers, or sales
• Translating a single internal roadmap to multiple audience formats
• Auditing roadmap commitments for over-promise risk
• Building a now-next-later view of priorities
• Communicating roadmap changes to stakeholders
• Preparing a what-changed/what's-next memo

Inputs the advisor expects

• The internal roadmap (themes, initiatives, target dates, confidence)
• Target audience(s) for the communication
• Recent roadmap changes (added, removed, slipped)
• Cross-functional commitments (engineering, sales, marketing)

Clarify First

Before generating the roadmap communication, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• [ ] Target audience — board/exec, customer, sales, or engineering (selects the audience-format matrix row and granularity)
• [ ] Confidence band per item — commit, plan, aspire, or strategic intent (drives the language and over-promise guardrails)
• [ ] Recent changes — what was added, removed, or slipped since the last readout (drives the what-changed diff memo)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Workflows

Workflow 1 — Translate roadmap for a specific audience

• Capture the master roadmap with confidence bands.
• Run roadmap_audience_translator.py with target audience.
• Review the audience-specific output; tune language.

python3 roadmap-communicator/scripts/roadmap_audience_translator.py \
  --input roadmap.json --audience customer --format markdown

Workflow 2 — Apply confidence bands to commitments

• List proposed roadmap items.
• Run confidence_band_generator.py with team velocity history + estimation context.
• Adjust item commitments based on output (commit / aspire / explore).

python3 roadmap-communicator/scripts/confidence_band_generator.py \
  --input items.json --format markdown

Workflow 3 — Generate a roadmap diff report

• Capture previous roadmap snapshot + current roadmap.
• Run roadmap_diff_reporter.py to produce what-changed memo.

python3 roadmap-communicator/scripts/roadmap_diff_reporter.py \
  --previous roadmap_q1.json --current roadmap_q2.json --format markdown

Decision frameworks

Audience-format matrix

| Audience | Right format | Wrong format |

|----------|--------------|--------------|

| Board / exec | Themes + bets + KPIs (1 page) | Feature list |

| Customers / public | What's new + what's next (themes; no dates) | Internal commit list |

| Sales | Themes + competitive positioning + customer-ask coverage | Engineering jargon |

| Engineering | Themes + quarter commitments + scoped detail | Vague aspirations |

| Internal company | Themes + progress + asks | Confidential strategy |

| Partner / integrator | API-relevant changes + breaking-change calendar | All-up roadmap |

Same roadmap; different formats. Don't send the engineering commit list to customers.

Confidence bands

Apply per item:

| Band | Language | Audience expectation |

|------|----------|----------------------|

| Commit | "Will ship" with target date | Hold us to this |

| Plan | "Plan to ship" with target window | Confident but conditional |

| Aspire | "Investigating" / "Exploring" | Don't depend on this |

| Strategic intent | "We believe X matters" | Direction, not deliverable |

Common errors:

• Treating "plan" as "commit" — sets up disappointment
• Communicating "commit" as "plan" — under-delivers excitement
• No confidence band — every line read as commit

Now-next-later structure

A useful skeleton across audiences:

• Now (in progress, < 1 quarter): commit-level items
• Next (1-2 quarters out): plan-level items
• Later (2-4 quarters): aspire-level items
• Strategic intent (>4 quarters): direction only

This protects confidence: the closer in time, the firmer the commitment.

Themes vs features

Communicate at the right granularity:

• External / strategic: themes ("better collaboration")
• Customer-specific: outcomes ("you'll be able to X")
• Internal: features + tickets

Telling a customer "we're adding X in Q3" makes a commitment that may

not be precise enough. Telling the team "we're going to improve

collaboration somehow" is too vague.

Common engagements

"Help me write the customer roadmap section"

• Start with what they care about (outcomes, not features).
• Use themes + outcomes; avoid specific dates beyond the current quarter.
• Group: launching soon, in development, exploring.
• Avoid: features that depend on uncertain technical bets.
• Always include a "we'd love your input" hook.

"Help me prep the board roadmap section"

• Start with strategic themes (3-5).
• For each theme: what's shipped, what's coming, what's the bet.
• Tie to business outcomes (NRR impact, new revenue, cost saving).
• Surface 1-2 strategic risks transparently.
• End with 2-3 specific asks.

"Our customer is asking 'when will X ship?'"

• First check: is X actually committed? (Probably plan or aspire.)
• If commit: give a target window with caveats.
• If plan: "We're planning to ship in [window]; we'll know more by [date]."
• If aspire: "We're exploring; not in our committed roadmap."
• Document the customer asks; feed them back into prioritization.

Anti-patterns to avoid

• One-size-fits-all roadmap. Different audiences get over- or under-served.
• Date-only roadmap. Dates without confidence bands set up over-promise.
• Public commitments engineering didn't sign off on. Trust breaks.
• Roadmap that never changes. Reality changes; roadmap must.
• Roadmap silence between updates. Customers / sales speculate.
• Hiding strategic risks. Boards prefer honest risks over surprise misses.
• Big bang annual roadmap with no quarterly delta. Misses change cycles.
• Feature names instead of outcomes. "Notifications v2" tells the customer nothing.

References

• references/roadmap-communication-patterns.md — format catalog + when to use
• references/audience-specific-formats.md — per-audience templates
• references/now-next-later-and-themes.md — structural patterns

Related skills

• product-team/product-strategist — strategy upstream of roadmap
• product-team/agile-product-owner — sprint-level execution
• product-team/product-manager-toolkit — broader PM tooling
• c-level-advisor/cpo-advisor — CPO partnership
• c-level-advisor/ceo-advisor — CEO / board alignment
• business-growth/customer-success-manager — customer comms
• marketing/ skills — external messaging alignment