roadmap-planning

Convert strategy into a sequenced, outcome-driven roadmap with prioritized backlog and dependency map.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/RebelHawk-TK/DeepThinkTrader --skill roadmap-planning-rebelhawk-tk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: roadmap-planning
Source: https://github.com/RebelHawk-TK/DeepThinkTrader/tree/main/.agents/skills/roadmap-planning
Command: npx skills add https://github.com/RebelHawk-TK/DeepThinkTrader --skill roadmap-planning-rebelhawk-tk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and coordinate complex product initiatives by turning high-level strategy into a structured, executable roadmap that aligns stakeholders and guides cross-functional delivery toward measurable outcomes.

Core Features & Use Cases

  • Phase-based workflow that guides gathering inputs, defining epics, prioritizing initiatives, sequencing releases, and communicating the plan.
  • Output artifacts including a prioritized backlog, dependency map, and publishable roadmap for internal and external stakeholder alignment.
  • Use Case: A product team facing multiple competing initiatives can use this workflow to convert strategy into now/next/late commitments with clear hypotheses and success metrics.

Quick Start

Begin by gathering inputs and then follow the five-phase roadmap planning workflow to define, prioritize, and sequence epics, and finally publish your roadmap.

Frequently Asked Questions about roadmap-planning

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

FAQPage Schema
How do I turn product strategy into an executable roadmap?▼

To turn strategy into an executable roadmap, you need to gather business goals, customer problems, and technical constraints, then use a structured workflow to define epics, prioritize initiatives, and sequence releases across Now/Next/Later buckets.

What is the best way to prioritize epics for stakeholder alignment?▼

Prioritizing epics for stakeholder alignment requires assessing dependencies and mapping initiatives to measurable outcomes and OKRs, ensuring cross-functional teams share a clear understanding of what gets built and why.

How do I sequence product releases when facing competing initiatives?▼

Sequencing product releases across competing initiatives involves grouping defined epics into Now/Next/Later categories, assessing technical dependencies, and mapping work to clear hypotheses and success metrics for coordinated delivery.

What inputs do I need for quarterly roadmap planning?▼

Quarterly roadmap planning requires inputs from business goals, customer problems, and technical constraints to successfully align stakeholders and convert high-level strategy into a sequenced, outcome-driven plan.

What artifacts should a publishable roadmap include?▼

A publishable roadmap should include a prioritized backlog, a dependency map, and the sequenced Now/Next/Later release plan to achieve internal and external stakeholder alignment.

Can I use this roadmap planning approach for cross-functional teams?▼

Yes, this roadmap planning workflow is designed for cross-functional product teams during quarterly planning to align stakeholders, define epics, and guide delivery toward measurable outcomes.