roadmap-planning

Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.

5,125stars655forksUpdated 6/15/2026

Developer Tools #stakeholder-alignment #prioritization #strategy #roadmap #product-management #planning

Security Assessment

Safe(100/100)

Security Score100/100

About roadmap-planning

The roadmap-planning skill guides product managers through strategic roadmap creation by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing into a structured workflow. It transforms disconnected feature requests into cohesive, outcome-driven roadmaps that align stakeholders and communicate strategic intent, helping teams avoid "feature factory" roadmaps that lack customer-centric framing or strategic narrative.

This skill supports multiple roadmap formats including Now/Next/Later (for agile teams managing uncertainty), Theme-Based (for executive communication), and Timeline/Quarterly roadmaps (for resource planning). It emphasizes outcome-driven planning that ties initiatives to business and customer outcomes, provides transparent stakeholder alignment processes, and maintains flexibility to adapt based on discovery and delivery learnings.

Best suited for product managers building strategic roadmaps for exec review, prioritizing competing initiatives across multiple teams, or planning quarterly/half-year work sequences. The skill is designed for annual or quarterly planning cycles, post-strategy translation work, and stakeholder onboarding. It takes 45-90 minutes to complete and helps move teams from tactical feature lists to strategic communication tools that show what you're building, why it matters, and how it connects to business outcomes.

FAQ

When should I use roadmap-planning versus just managing my backlog?

Use roadmap-planning for strategic quarterly or annual planning cycles when you need to align stakeholders and communicate direction. Use backlog management for tactical sprint planning and day-to-day execution. Roadmaps are strategic plans that show themes and initiatives; backlogs contain granular user stories and tasks.

What if my product strategy isn't clear yet?

Don't use this skill if strategy is unclear. Run a product-strategy-session first to establish strategic direction, then use roadmap-planning to translate that strategy into an executable plan. Roadmap planning requires strategic inputs like business goals and customer problems to be effective.

Is the roadmap a commitment or can it change?

Roadmaps are strategic plans, not contracts or commitments. They should evolve quarterly based on learnings from discovery and delivery. The Now/Next/Later format explicitly manages confidence levels, with current quarter work being committed while future quarters remain flexible.

What's the difference between a strategic roadmap and a feature-based roadmap?

A strategic roadmap frames problems and outcomes, organizing work by themes or initiatives with clear hypotheses and success metrics. A feature-based roadmap just lists features (like "Dark mode" or "SSO") without context, creating an anti-pattern that lacks strategic narrative and doesn't explain why the work matters or what customer problems it solves.

How long does it take to create a roadmap using this skill?

The estimated time is 45-90 minutes, depending on the number of competing initiatives, team complexity, and planning horizon (quarterly vs. half-year vs. annual). The skill orchestrates multiple sub-processes including prioritization, epic definition, and sequencing.