roadmap-planning

Convert feature requests into prioritized epics and sequenced Now/Next/Later roadmaps.

1|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/yuyuxinli/moodcoco --skill roadmap-planning-yuyuxinli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-planning
Source: https://github.com/yuyuxinli/moodcoco/tree/main/.claude/skills/roadmap-planning
Command: npx skills add https://github.com/yuyuxinli/moodcoco --skill roadmap-planning-yuyuxinli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams struggle to turn scattered feature requests and stakeholder demands into a coherent, outcome-driven roadmap that aligns with business goals, technical constraints, and delivery capacity. This workflow provides a repeatable process to gather inputs, define epics with hypotheses and success metrics, prioritize by impact and effort, sequence releases with dependencies, and align stakeholders around a clear plan.

Core Features & Use Cases

  • Structured five-phase workflow: Gather inputs, define epics, prioritize, sequence, and communicate a roadmap over 1-2 weeks.
  • Outcome-driven epics: Convert features into hypotheses with success metrics and effort estimates (T-shirt sizing).
  • Prioritization & sequencing: Apply frameworks (RICE/ICE/Value-Effort), map dependencies, and create Now/Next/Later or quarter-based timelines.
  • Stakeholder alignment: Prepare presentation artifacts, collect feedback, and iterate to produce a validated roadmap.
  • Use Case: Prioritizing 10–15 initiatives across three teams for a Q2 roadmap that must satisfy retention and enterprise acquisition goals.

Quick Start

Create a prioritized Now/Next/Later roadmap for the next two quarters by listing business goals, top customer problems, candidate epics with hypotheses, effort estimates, and a RICE-style prioritization so you can sequence releases and surface dependencies for stakeholder review.

Frequently Asked Questions about roadmap-planning

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

FAQPage Schema
How do I turn scattered feature requests into an outcome-driven product roadmap?

To turn scattered feature requests into an outcome-driven product roadmap, gather business goals and validated customer problems, define epics with success metrics, prioritize initiatives using RICE or Value-Effort frameworks, and sequence releases across teams.

What is the best way to prioritize epics and map dependencies for quarterly release planning?

The best way to prioritize epics for release planning is to apply frameworks like RICE or ICE, estimate effort with T-shirt sizing, map technical dependencies, and sequence initiatives into a Now/Next/Later or quarter-based timeline to align stakeholders.

Can I use this workflow to align multiple teams around a single release plan?

Yes, you can align multiple teams around a single release plan by mapping cross-team dependencies, sequencing epics based on technical constraints and delivery capacity, and generating presentation artifacts to collect stakeholder feedback and iterate.

How does defining epic hypotheses improve product strategy and stakeholder alignment?

Defining epic hypotheses improves product strategy by converting feature requests into outcome-driven assumptions with specific success metrics, ensuring that prioritized initiatives directly satisfy business goals like retention or enterprise acquisition during stakeholder alignment.

What inputs do I need to create a sequenced Now/Next/Later roadmap?

To create a sequenced Now/Next/Later roadmap, you need inputs including business outcomes, validated customer problems, effort estimates, technical constraints, and stakeholder requests to produce prioritized epics, dependency graphs, and release timelines.