Menu

Individual skill

product-roadmap

0upvotes

Turns product strategy into a themed Now/Next/Later roadmap with explicit trade-offs, confidence levels, and no committed dates beyond one quarter. Use when someone asks "build our product roadmap", "turn these priorities into a roadmap", "execs want committed ship dates for next year", or needs to communicate direction without over-promising. Do NOT use for company-wide annual operating plans - use annual-plan instead; for defining the goals a roadmap serves, use okr-builder; for scheduling work inside a sprint, use sprint-planning.

skills/product-roadmap/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Product Roadmap

A roadmap is a communication tool, not a promise to ship a feature list on fixed dates. The costly failure it prevents is double-sided: a Gantt chart of dated features sets the team up to publicly "miss the roadmap" within two months, while a roadmap with no trade-offs is a wishlist that aligns nobody. This skill builds one that aligns the organization around outcomes and survives contact with reality.

## Operating procedure

### Step 1: Gather inputs and anchor to strategy

Collect before building; where an input is missing, that is upstream work, not a blank to improvise:

- Vision - where the product is going in 1-3 years.
- Goals - the 2-4 outcomes for this period (growth, retention, expansion). More than 4 goals means no goals; send goal-setting itself to okr-builder.
- Target users and problems - who is served and what pain is being solved.
- The candidate list: everything currently being considered, with rough effort and any evidence of value.