roadmap-management

Name: roadmap-management
Availability: InStock
Author: chelleboyer

Automates quarterly roadmap planning and prioritization for product teams using RICE, MoSCoW, and ICE frameworks.

Updated Jan 11, 2026

Search Tags:#planning #frameworks #roadmap #prioritization #okr #stakeholders

Ready to run

npx skills add https://github.com/chelleboyer/reachy_mini_retail_assistant --skill roadmap-management-chelleboyer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: roadmap-management
Source: https://github.com/chelleboyer/reachy_mini_retail_assistant/tree/main/skills/product-management/skills/roadmap-management
Command: npx skills add https://github.com/chelleboyer/reachy_mini_retail_assistant --skill roadmap-management-chelleboyer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roadmap planning often suffers from misalignment, unclear priorities, and brittle tradeoffs. This skill provides a structured approach to building, prioritizing, and communicating roadmaps so teams stay aligned and stakeholders understand decisions.

Core Features & Use Cases

Framework-based prioritization: Use RICE, MoSCoW, and ICE to score initiatives and justify sequencing.
OKR-aligned planning: Map initiatives to Objectives and Key Results to tie work to outcomes.
Dependency & capacity awareness: Identify and manage cross-team dependencies, capacity constraints, and risk-prone items.
External communication: Produce clear roadmaps (Now/Next/Later, quarterly themes, timelines) to share with leadership and exec teams.

Quick Start

Create a four-quarter roadmap using Now/Next/Later, map top initiatives to your OKRs, and share the prioritization rationale with stakeholders.

Frequently Asked Questions about roadmap-management

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

FAQPage Schema

How do I prioritize a product roadmap using RICE or MoSCoW frameworks?▼

Roadmap prioritization using RICE or MoSCoW scores initiatives to justify sequencing and align stakeholders. Applying these frameworks provides objective criteria for evaluating reach, impact, confidence, and effort, making tradeoff decisions transparent.

What is the best way to align quarterly roadmap themes with OKRs?▼

Aligning quarterly roadmap themes with OKRs maps planned initiatives directly to Objectives and Key Results. This structured planning ties work to measurable outcomes, ensuring product delivery consistently supports strategic goals across the organization.

How do I communicate roadmap tradeoffs to stakeholders across engineering and marketing?▼

Communicating roadmap tradeoffs requires producing clear artifacts like Now/Next/Later or quarterly timelines. This structured approach clarifies prioritization rationale, addresses dependency constraints, and ensures leadership across functions understands decisions.

Can I manage cross-team dependencies and capacity constraints during roadmap planning?▼

Roadmap planning supports managing cross-team dependencies and capacity constraints to identify risk-prone items. This dependency awareness allows teams to sequence work realistically, preventing bottlenecks across engineering, design, and marketing functions.

What is a Now/Next/Later roadmap and when should I use it?▼

A Now/Next/Later roadmap is a communication artifact organizing initiatives by time horizon without strict dates. Use this format to share prioritization rationale with leadership, maintaining flexibility while setting clear expectations for delivery.

Does roadmap planning work for aligning initiatives across engineering, design, and marketing teams?▼

Roadmap planning aligns initiatives across engineering, design, and marketing by mapping work to shared OKRs. This structured approach highlights cross-team dependencies and capacity constraints, producing a shareable artifact that clarifies tradeoffs.