roadmap-management_skill

Overview

This skill helps product teams plan, prioritize, and communicate roadmaps using established frameworks like RICE, MoSCoW, ICE, Now/Next/Later, and timeline views. It provides practical guidance for mapping dependencies, estimating capacity, and presenting tradeoffs so roadmaps stay strategic and deliverable. Use it to create, re-prioritize, or present roadmaps with confidence.

How this skill works

The skill evaluates initiatives against chosen prioritization frameworks (RICE, ICE, MoSCoW, value vs effort) and recommends rank order and grouping. It inspects dependencies, assigns owners and need-by dates, and models capacity against team availability to surface overcommitment. It also formats recommended outputs into Now/Next/Later, quarterly themes, OKR-aligned lists, or timeline views for stakeholder communication.

When to use it

• Creating an initial roadmap for a quarter or product launch
• Reprioritizing a backlog after new data or leadership direction
• Mapping dependencies across teams, vendors, or technical work
• Choosing a presentation format (Now/Next/Later, quarterly themes, timeline)
• Explaining tradeoffs and what must be cut to stay on schedule

Best practices

• Pick one primary prioritization framework for consistency; use RICE for data-driven compares and ICE for quick decisions
• List and assign owners for every dependency and set explicit need-by dates
• Estimate capacity conservatively (60–70% of engineer time for planned work) and reserve buffer for unplanned work
• Align roadmap items to themes or OKRs when communicating strategy to executives
• Batch roadmap updates on a cadence (monthly or quarterly) to avoid whiplash

Example use cases

• Score a mixed backlog of feature requests with RICE to produce a defensible priority list
• Convert prioritized initiatives into a Now/Next/Later external roadmap for leadership
• Map technical and team dependencies for a cross-functional release and assign owners
• Build a quarterly themes roadmap tied to company OKRs for executive review
• Run a capacity check to decide what to cut when commitments exceed team bandwidth