pm-stage-09-roadmap

Synthesize approved MVP artifacts into release horizons and decision gates.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/pingmepi/pm-os --skill pm-stage-09-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-stage-09-roadmap
Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-stage-09-roadmap
Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-stage-09-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of transitioning from a validated MVP to a structured, long-term product strategy without losing focus or inflating scope.

Core Features & Use Cases

  • Strategic Sequencing: Automatically synthesizes approved product artifacts into release horizons (V1, V2, Later).
  • Decision Governance: Establishes measurable gates and dependencies to ensure roadmap items are backed by evidence and metrics.
  • Use Case: After completing your MVP pipeline, use this skill to define the next phase of growth, ensuring your roadmap remains aligned with your original success hypothesis and technical constraints.

Quick Start

Invoke the pm-stage-09-roadmap skill to generate a product roadmap based on your currently approved MVP pipeline.

Frequently Asked Questions about pm-stage-09-roadmap

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

FAQPage Schema
How do I generate a product roadmap after completing an MVP pipeline?

To generate a product roadmap after MVP, you synthesize approved artifacts like briefs and PRDs to sequence post-MVP growth into release horizons. This process establishes structured V1, V2, and Later phases while aligning with your original success hypothesis.

What is strategic sequencing in post-MVP product management?

Strategic sequencing in product management is the process of synthesizing approved MVP artifacts into structured release horizons. It defines V1, V2, and Later phases to ensure your post-MVP growth maintains focus without inflating scope.

How do I establish decision gates for a product roadmap?

You establish decision gates for a product roadmap by defining measurable gates and dependencies based on metrics plans. This governance ensures roadmap items remain backed by evidence and aligned with technical constraints.

Do I need approved PRDs and metrics plans to build a structured roadmap?

Yes, you need approved PRDs and metrics plans to build a structured roadmap. The generation operates on the product-definition pipeline, requiring validated local project state artifacts to sequence release horizons effectively.

Can I use this roadmap generation approach without a stage-gating protocol?

No, you cannot use this approach without a stage-gating protocol. It requires strict adherence to the PM-OS stage-gating protocol for artifact validation to ensure your roadmap items are backed by evidence.

What's the best way to transition from a validated MVP to a long-term strategy?

The best way to transition from a validated MVP to a long-term strategy is by synthesizing approved artifacts into release horizons. This prevents scope inflation by establishing measurable decision gates and sequencing post-MVP growth.