roadmap-planning

Orchestrate a multi-phase product roadmap planning workflow from inputs to stakeholder communication.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/MMXC/openclaw-back --skill roadmap-planning-mmxc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: roadmap-planning
Source: https://github.com/MMXC/openclaw-back/tree/main/pm-skills/skills/roadmap-planning
Command: npx skills add https://github.com/MMXC/openclaw-back --skill roadmap-planning-mmxc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires epic-hypothesis, prioritization-advisor, and includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill guides product managers through the complex process of creating a strategic product roadmap, transforming disconnected feature requests into a cohesive, outcome-driven plan that aligns stakeholders and communicates clear strategic intent.

Core Features & Use Cases

  • Orchestrates a structured 5-phase process: From gathering inputs to communicating the final roadmap.
  • Integrates with other skills: Leverages epic-hypothesis and prioritization-advisor for key steps.
  • Focuses on outcomes: Ensures the roadmap clearly ties initiatives to business goals and customer problems.
  • Use Case: A product manager needs to build a Q2 roadmap for 15 competing initiatives. This Skill will help them gather inputs, define epics with clear hypotheses, prioritize them using a chosen framework, sequence them logically, and present a compelling roadmap to executives.

Quick Start

Use the roadmap-planning skill to guide me through building our Q2 product roadmap, starting with gathering inputs.

Frequently Asked Questions about roadmap-planning

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

FAQPage Schema
How do I build a strategic product roadmap that aligns stakeholders?▼

Strategic product roadmap planning orchestrates a multi-phase workflow that transforms disconnected feature requests into an outcome-driven plan, ensuring alignment with business goals and customer problems while preventing HiPPO prioritization.

What is the best way to prioritize competing product initiatives?▼

Prioritizing competing product initiatives requires defining clear epic hypotheses and applying a structured prioritization framework to sequence them logically, ensuring selected features drive desired business outcomes.

How do I avoid feature-driven roadmaps and HiPPO prioritization?▼

Avoiding feature-driven roadmaps and HiPPO prioritization requires shifting focus to business outcomes, using structured epic hypothesis definitions and framework-based prioritization to sequence initiatives objectively.

Can I use this roadmap planning process for a quarterly Q2 release?▼

Yes, this roadmap planning workflow suits quarterly Q2 releases by guiding product managers through a 1-2 week structured process to gather inputs, define epics, and sequence 15 competing initiatives for executive presentation.

Do I need epic hypotheses to start product roadmap planning?▼

Yes, defining epic hypotheses is required during product roadmap planning to ensure initiatives tie directly to customer problems and business outcomes before stakeholder communication.