roadmap-planning

Plan strategic product roadmaps with hypothesis-driven epics and dependency sequencing.

Updated Aug 18, 2024
One-click install
npx skills add https://github.com/ch-m-n/dotfile --skill roadmap-planning-ch-m-n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-planning
Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/roadmap-planning
Command: npx skills add https://github.com/ch-m-n/dotfile --skill roadmap-planning-ch-m-n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered feature requests, competing stakeholder demands, and unclear sequencing into a cohesive strategic roadmap that prioritizes outcomes and aligns stakeholders without resorting to a feature-factory approach.

Core Features & Use Cases

  • Five-phase decision framework: Gather inputs, define hypotheses, prioritize initiatives, sequence releases, and communicate the plan with guided activities for each phase.
  • Hypothesis-driven epics with success metrics: Use components such as epic hypotheses and prioritization frameworks to score and tag initiatives with business outcomes before sequencing.
  • Stakeholder-ready storytelling: Sequence dependencies, validate with engineering, and craft a presentation-ready narrative that highlights strategic intent, risks, and why certain initiatives lead over others.

Quick Start

Ask the roadmap-planning skill to gather OKRs, customer problems, prioritized epics, and logging dependencies before sequencing the next quarterly releases.

Frequently Asked Questions about roadmap-planning

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

FAQPage Schema
How do I build an outcome-driven product roadmap from scattered feature requests?

An outcome-driven roadmap prevents disjointed feature requests by mapping documented inputs, customer pains, and technical constraints into hypothesis-driven epics. Initiatives are scored using prioritization frameworks before being sequenced into a cohesive release plan.

What is the best way to align stakeholders during quarterly release planning?

Stakeholder alignment is achieved by crafting a presentation-ready narrative that communicates strategic intent, validates dependencies with engineering, and explains why certain initiatives lead over others to prevent disjointed feature requests.

Can I use hypothesis-driven epics for half-year release plans with multiple teams?

Yes, hypothesis-driven epics scale for half-year release plans by tagging initiatives with business outcomes and success metrics before dependency sequencing, ensuring technical constraints and business goals remain mapped across multiple teams.

How do prioritization frameworks help sequence product releases?

Prioritization frameworks score hypothesis-driven epics against business goals and customer pains, allowing product managers to logically order initiatives based on strategic value, dependencies, and technical constraints before finalizing the roadmap.

What inputs do I need before creating a strategic product roadmap?

Creating a strategic product roadmap requires documented inputs from OKRs, customer discovery findings, technical constraints, and stakeholder requests to ensure epic planning and release sequencing accurately reflect business goals and dependencies.