pm-roadmap

Creates and critiques outcome-oriented product roadmaps using Now-Next-Later formats tied to strategy.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-roadmap-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-roadmap
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/pm/deliverables/roadmap
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-roadmap-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product roadmaps often degrade into dated feature lists that promise certainty, go stale within a quarter, and confuse strategy with backlog tasks. This Skill guides the creation or critique of roadmaps that communicate outcomes, themes, and honest confidence levels instead of false-precision commitments. ## Core Features & Use Cases - Context Gating: Establishes strategy, OKRs, audience, horizon, and delivery context before drafting, so format and detail match the actual planning situation. - Outcome-First Structure: Organizes work as themes and initiatives traced to strategic goals, with features treated as swappable bets rather than commitments. - Format Decision Guidance: Surfaces trade-offs between Now-Next-Later, theme-based, and timeline views, plus audience-specific views for internal teams, executives, and customers. - Use Case: A product manager preparing a quarterly planning review asks for a roadmap restructure; the Skill produces a Now-Next-Later view where each theme links to a key result, then hands off to prioritization and metric-validity audits. ## Quick Start Ask the assistant to build or review a product roadmap for your team, describing your strategy, target audience, and planning horizon.

Frequently Asked Questions about pm-roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a product roadmap without fixed dates?▼

Use a Now-Next-Later format that organizes work by confidence level rather than calendar dates. Near-term items are committed, while later items are marked as bets, keeping direction stable without manufacturing false certainty.

What is the difference between a roadmap and a backlog?▼

A roadmap communicates strategic direction as themes and outcomes, while a backlog holds tasks, bugs, and tickets. If roadmap items carry story points or bug fixes, they belong in the backlog instead.

Should executives and customers see the same roadmap?▼

No. Create different views of one source of truth: internal teams get detail and dependencies, executives get themes and strategic linkage, and customers get value and direction without dates or internals.

When is a timeline or Gantt roadmap appropriate?▼

Timeline views fit fixed-date commitments like compliance deadlines, contracts, and cross-team dependencies. They should remain an internal execution layer, since presenting them publicly reads as a promise.

How often should a product roadmap be updated?▼

Treat the roadmap as a living document with scheduled quarterly reviews plus event-triggered replanning. Major discovery findings, competitor moves, and strategy shifts should all trigger updates rather than waiting for the calendar.