po-product-roadmap

Define structured product roadmaps with themes, timelines, milestones, and dependencies.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Yukine5377/common --skill po-product-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: po-product-roadmap
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/po-product-roadmap
Command: npx skills add https://github.com/Yukine5377/common --skill po-product-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roadmapping guides teams by translating business goals into a time-bound plan that coordinates actions across stakeholders and engineering, ensuring everyone understands priorities and the rationale behind them.

Core Features & Use Cases

  • Frameworks for prioritization (RICE, MoSCoW, Now/Next/Later) to structure decisions.
  • Theme-based organization (Acquisition, Retention, Revenue) to group related work.
  • Roadmap outputs and governance (vision context, timeline, feature detail, milestones, dependencies, and resource planning).

Quick Start

Create a roadmap draft by outlining themes, prioritizing a small set of features, and mapping them to quarters.

Frequently Asked Questions about po-product-roadmap

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

FAQPage Schema
What is the best way to structure a product roadmap for stakeholder alignment?

A product roadmap aligns stakeholders by translating business goals into a time-bound plan that communicates priorities and rationale. Theme-based organization groups related work to ensure teams understand what is built, in what order, and why.

How do I prioritize features on a product roadmap?

You can prioritize roadmap features using frameworks like RICE, MoSCoW, or Now/Next/Later. These frameworks structure decisions by scoring features based on reach, impact, confidence, effort, or mandatory versus optional categories.

Can I use a product roadmap for quarterly planning and cross-functional alignment?

Yes, a product roadmap is applicable to quarterly planning and cross-functional alignment across business and engineering teams. It coordinates actions by mapping milestones, dependencies, and resource planning to specific timeline views.

How do I organize a roadmap using themes like Acquisition or Retention?

Theme-based organization groups related work into categories such as Acquisition, Retention, and Revenue. This approach structures the roadmap around strategic business objectives rather than isolated feature lists.

What should a strategic roadmap include for engineering and business teams?

A strategic roadmap should include vision context, timeline views, feature detail cards, milestones, dependencies, and resource planning. These elements coordinate actions and ensure everyone understands priorities across teams.

When do I need a roadmap with milestones and dependencies?

You need a roadmap with milestones and dependencies when coordinating cross-functional teams for quarterly planning. Mapping dependencies ensures engineering teams understand sequence constraints and resource allocation limits.