Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fbarrento/product-roadmap
Produces product/roadmap.md — a deliberate sequence of intended value slices across capabilities, ordered by priority, dependency, and time-to-market.
Passed 19 of 22 test cases with the skill, and 8 of 22 without it.
and 21 more in the full report
13 fixed7 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Our strategy emphasizes time-to-market urgency. Does this mean roadmap.md should include target delivery dates or milestone deadlines?
| Checked | Without skill | With skill |
|---|---|---|
| Explains time-to-market as finding the shortest path to shippable value rather than target dates. | Missed | Passed |
| Refuses to include milestone deadlines or release schedules. | Missed | Passed |
The instructions your model reads when the skill loads.
product-roadmap produces product/roadmap.md — the product's sequenced
intent: which value slices the product should ship next, across which
capabilities, in what order, and why. It is authored top-down from the
strategy and the capability map. It is advisory — a roadmap item is the
recommended starting point for a change, never a gate. It is product-level
state, a sibling of vision.md and strategy.md, and it can be re-run to
reconcile with a changed strategy or capability map.
Generic skill — hard-codes no path. Resolve the state-tree root from the
project's CLAUDE.md (project-declared paths, DESIGN_PRODUCT_PIPELINE.md §2);
default docs/, and say which you used. {state-root} is that root, so the
roadmap lives at {state-root}/product/roadmap.md, the strategy at
{state-root}/product/strategy.md, the vision at
{state-root}/product/vision.md, and the capability map is the set of
{state-root}/capabilities/{slug}/README.md.
Before producing a roadmap you MUST, in order:
product/strategy.md — it must exist and be
status: approved (the strategy itself transitively requires an approved
vision). Read the capability map — the set of
capabilities/{slug}/README.md. If there is no approved strategy, or no
capability map — STOP. The roadmap sequences value slices across
capabilities to serve the strategy; without both it has nothing to sequence
and no criterion to sequence by. Run product-strategy / capability-map
first.changes/ folders to assemble it.Hard rules:
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.