---
name: roadmap-language-reviewer
description: >
  Reviews roadmap language for external-readiness and PMM consistency.
  Use when a roadmap deck is being prepared for customers, analysts, or board.
  Also consider when sales shares roadmap slides with prospects during deal cycles.
  Suggest when internal roadmap documents use engineering jargon that will confuse external audiences.
department: product
agent: pmm
version: 1.0.0
complexity: medium
related-skills:
  - sales-playbook-messaging
  - launch-narrative-builder
  - positioning-crafter
triggers:
  - "review roadmap language"
  - "roadmap copy review"
  - "roadmap wording"
  - "check roadmap language"
  - "roadmap messaging"
---

# roadmap-language-reviewer

## Agent: PMM
L2 product marketing manager responsible for competitive intelligence, positioning, GTM planning, pricing strategy, launch narrative, and sales enablement.

Department ethos: [ideal-product.md](../../../../departments/product/ideal-product.md)

## Skill Description
Reviews roadmap language for external-readiness and PMM consistency, ensuring that roadmap items shared with customers, analysts, prospects, or board members use buyer-centric language aligned with current positioning.

## When to Use
- A roadmap presentation is being prepared for a customer advisory board, analyst briefing, or board meeting.
- Sales is sharing roadmap slides with prospects as part of a deal cycle.
- Product publishes a public-facing roadmap or changelog that references upcoming capabilities.
- Quarterly planning produces new roadmap items that will eventually be communicated externally.
- An account team needs to discuss future capabilities with a strategic customer.

## Workflow
1. Receive the roadmap document or deck from product management. Identify which items are marked for external sharing.
2. Review each roadmap item against three criteria: does it use buyer language (not engineering jargon), does it align with current positioning and messaging hierarchy, and does it avoid over-committing on dates or scope.
3. Rewrite item titles and descriptions in outcome-oriented language. Replace "implement X backend service" with "enable Y workflow for Z persona."
4. Flag any items that conflict with current positioning or inadvertently reveal competitive vulnerabilities. Recommend removal or reframing.
5. Add appropriate disclaimers for forward-looking items. Ensure language uses "planned" or "exploring" rather than commitments, to avoid contractual exposure.
6. Review the sequencing narrative. Ensure the roadmap tells a coherent story about product direction that reinforces the positioning, not just a list of features.
7. Return the reviewed document to product management with tracked changes and a summary of material edits.

## Anti-Patterns
- **Reviewing only titles and ignoring descriptions.** *Why: Titles may pass the jargon check while descriptions contain internal terminology that confuses or alarms external audiences.*
- **Approving committal language on unconfirmed items.** *Why: Roadmap promises that are shared externally become de facto commitments; missed commitments erode customer trust and create legal risk.*
- **Reviewing the roadmap in isolation from positioning.** *Why: Roadmap language that drifts from positioning creates a secondary narrative that competitors and analysts may use against you.*
- **Treating this as a copy-edit rather than a strategic review.** *Why: The roadmap shapes market perception of product direction; it is a positioning exercise, not a grammar exercise.*

## Output

**Success:**
- Reviewed roadmap document with all external-facing items rewritten in buyer-centric, positioning-aligned language.
- Forward-looking disclaimers applied to uncommitted items.
- Summary of material edits returned to product management for awareness.

**Failure:**
- Engineering jargon survives into the external presentation, confusing buyers or leaking implementation details.
- Committal language on uncertain items creates customer expectations the product team cannot meet.
- Roadmap reviewed but not aligned with current positioning, introducing messaging inconsistency.

## Related Skills
- positioning-crafter
- prd-executive-summary
- internal-comms-broadcaster-pmm
- launch-narrative-builder
- [`sales-playbook-messaging`](../sales-playbook-messaging/SKILL.md) — sibling skill under the same agent — combine with sales-playbook-messaging for end-to-end coverage
- [`launch-narrative-builder`](../launch-narrative-builder/SKILL.md) — sibling skill under the same agent — combine with launch-narrative-builder for end-to-end coverage
- [`positioning-crafter`](../positioning-crafter/SKILL.md) — sibling skill under the same agent — combine with positioning-crafter for end-to-end coverage