Transform a prioritised initiative list into a compelling strategic roadmap narrative. Use when asked to write a roadmap narrative, explain the product roadmap to non-technical stakeholders, connect roadmap items to company goals, or produce an exec-shareable roadmap story. Produces a themed narrative with strategic context, quarter progression arc, an executive summary, and a 'what's not on the roadmap' section.
📚 Based on Product Roadmaps Relaunched (Lombardo, McCarthy, Wax, Connors)
“Write a roadmap narrative.”“Explain the product roadmap to non-technical stakeholders.”“Produce an exec-shareable roadmap story.”“Run this skill in your browser: https://mohitagw15856.github.io/pm-claude-skills/skill/roadmap-narrative.html”
What to give it
▸Prioritised initiative list — with rough timelines or quarters
▸Company OKRs or strategic priorities — to connect roadmap to company goals
▸Audience — all-hands, board, investors, sales team — changes tone and depth
▸Items explicitly NOT on the roadmap(optional) — optional but strengthens credibility
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Every initiative in the input maps to a strategic theme
✓The executive summary can stand alone and be repeated correctly after one reading
✓Progression narrative shows causal links between quarters (not just chronological listing)
✓"What's not on the roadmap" section includes at least 2 items with clear rationale
✓Language throughout is free of engineering jargon — tested by asking: "could a CFO repeat this?"
⚠️ What it refuses to do
Do not produce a list of features with dates and call it a narrative — every initiative must connect to a strategic theme
Do not omit the "what's not on the roadmap" section — without it, the narrative lacks strategic discipline
Do not write progression as a chronological list — show causal links between quarters (Q1 enables Q2 because…)
Do not write the executive summary last and treat it as a summary — write it as the version stakeholders will repeat
Do not let orphaned initiatives appear without a theme — either create a theme or flag the gap explicitly
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcp
Example output
Input: H2 roadmap for a B2B analytics product. Themes: self-serve onboarding, an integrations marketplace, and enterprise SSO/audit logs. Audience: the exec team and key customers. We want the story, not a feature list. · generated by claude-sonnet-4-6