roadmap-planning

Convert a ranked backlog into a sequenced outcome-driven product roadmap with dependency mapping.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill roadmap-planning-brunol28
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: roadmap-planning
Source: https://github.com/BrunoL28/product-onboarding-skill/tree/main/skills/roadmap-planning
Command: npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill roadmap-planning-brunol28

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A prioritized backlog tells you what matters most, but not what ships first, what it proves, or how it ladders to business outcomes. This Skill turns a ranked candidate list into a sequenced roadmap with dependencies mapped, a thin walking-skeleton first slice, engineering-validated capacity, and confidence decay stated on the artifact itself. ## Core Features & Use Cases - Format selection by audience: Choose Now/Next/Later, theme-based, or timeline formats deliberately, recording the rejected option and why. - Mandatory outcome column: Every initiative row carries a measure, baseline, and direction, or a visible blank with a named owner. - Dependency mapping and walking skeleton: Render hard and soft dependencies in ASCII and define a thin end-to-end first slice that proves the whole path. - Capacity gate: Engineering sizes are recorded verbatim or left blank; the model never estimates on engineering's behalf. - Use Case: After a RICE prioritization session ranks seven initiatives, use this Skill to sequence them into a Now/Next/Later roadmap with a dependency map, an open capacity gate, and a strategic narrative for the steering group. ## Quick Start Turn my prioritized backlog into a Now/Next/Later roadmap with dependencies mapped and a walking skeleton first slice.

Frequently Asked Questions about roadmap-planning

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

FAQPage Schema
How do I turn a prioritized backlog into a product roadmap?▼

Feed the ranked candidate list, business goals, team constraints, and known dependencies into the roadmap-planning skill. It groups items into initiatives with outcomes, maps dependencies, defines a walking-skeleton first slice, and sequences work into Now, Next, and Later horizons.

What roadmap format should I use for executives?▼

Theme-based formats suit executive or board audiences where narrative matters more than items. Now/Next/Later fits when uncertainty is real, and timeline formats should only be used when a hard external date exists, such as a regulator or contract deadline.

What is a walking skeleton in roadmap planning?▼

A walking skeleton is a thin end-to-end first release slice that touches every layer the user journey needs without thickening any of them. It must be demonstrable to a real user; otherwise it is a foundation, which proves nothing about the path.

Does the roadmap skill estimate engineering capacity or delivery dates?▼

No. Capacity and effort numbers must come from engineering and are recorded verbatim or left blank with the gate flagged open. The skill never generates delivery dates, estimates, or commitments on anyone's behalf.

What inputs does roadmap planning require before starting?▼

It requires a ranked candidate list with its scoring framework, the business goals or OKRs initiatives ladder to, the delivery constraint of teams and horizon, known dependencies, and the target audience. Unranked piles should go through prioritization first.

When should I not use a timeline roadmap?▼

Avoid timeline formats when no external party set a date, because every date reads as a commitment and slippage becomes a credibility event. Use Now/Next/Later with a confidence-decay key instead so stakeholders understand what each horizon is worth.