roadmap-management

Plan and prioritize product roadmaps using RICE, MoSCoW, and ICE frameworks.

7|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/Epiphytic/ai-plugin-translator --skill roadmap-management-epiphytic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-management
Source: https://github.com/Epiphytic/ai-plugin-translator/tree/main/packages/core/test/fixtures/regression-output/knowledge-work-plugins/product-management/skills/roadmap-management
Command: npx skills add https://github.com/Epiphytic/ai-plugin-translator --skill roadmap-management-epiphytic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product managers turn competing ideas, feature requests, and strategic goals into clear, prioritized roadmaps that align teams and communicate tradeoffs effectively.

Core Features & Use Cases

  • Roadmap Planning: Create Now/Next/Later, quarterly theme, OKR-aligned, and timeline-based roadmap structures.
  • Prioritization Frameworks: Apply RICE, MoSCoW, ICE, and value versus effort analysis to evaluate initiatives.
  • Dependency & Capacity Management: Map dependencies, assess team capacity, and communicate roadmap changes with stakeholders.
  • Use Case: A product team can use this Skill to prioritize a backlog of feature requests, identify dependencies, and present a realistic quarterly roadmap to leadership.

Quick Start

Use the roadmap management skill to prioritize my product backlog and create a Now, Next, Later roadmap with tradeoffs.

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 backlog using RICE and MoSCoW frameworks?

Product backlog prioritization applies RICE, MoSCoW, and ICE frameworks to evaluate competing initiatives by scoring reach, impact, confidence, and effort. This structures feature requests into clear delivery priorities, helping teams align on what to build next.

What is the best way to structure a product roadmap for stakeholder communication?

The best way to structure a product roadmap for stakeholder communication is using Now/Next/Later, quarterly theme, or OKR-aligned formats. These structures communicate tradeoffs and delivery priorities effectively without overwhelming stakeholders with rigid timelines.

Can I map team dependencies and capacity when planning a quarterly product roadmap?

Yes, dependency and capacity management maps cross-team dependencies and assesses available capacity during quarterly product roadmap planning. This identifies bottlenecks early, ensuring the roadmap reflects realistic delivery expectations and structured prioritization.

How do I create a Now Next Later roadmap from feature requests?

Creating a Now/Next/Later roadmap from feature requests requires evaluating each initiative using value versus effort analysis and ICE scoring. Prioritized items are then organized into immediate, near-term, and future delivery buckets to guide strategic product decisions.

When should I use ICE over RICE for product prioritization?

Use ICE over RICE for product prioritization when you need a simpler evaluation method focused on impact, confidence, and ease, omitting reach. RICE is better for initiatives where audience size significantly affects the overall strategic value calculation.

Why does my product roadmap fail to align with strategic OKRs?

Product roadmaps fail to align with strategic OKRs when feature requests lack structured prioritization methods like RICE or MoSCoW. Applying these frameworks evaluates initiatives against strategic goals, ensuring roadmap themes directly support defined objectives.