SkillAgentSearch skills...

roadmap-planning

Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill roadmap-planning

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Universal

Tags

Our assessment of roadmap-planning

roadmap-planning scores 93/100 on our quality scale, 9th of 60 Product Management skills we index (top 15%).

Its SKILL.md is 19 KB long, well organised into 38 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so roadmap-planning is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

roadmap-planning compared with similar skills

All 4 of these similar skills score higher than roadmap-planning; compare them before choosing.

SkillScoreStarsUpdatedFormat
roadmap-planning (this skill)by deanpeters937.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install roadmap-planning?
Run npx skills add deanpeters/Product-Manager-Skills --skill roadmap-planning. The install tabs above show the steps for each supported agent.
Which AI agents does roadmap-planning work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is roadmap-planning safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is roadmap-planning still maintained?
The repository was last updated about 3 months ago, so roadmap-planning is actively maintained.

name: roadmap-planning argument-hint: "[product and planning horizon]" description: Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute. intent: >- Guide product managers through strategic roadmap planning by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing skills into a structured process. Use this to move from disconnected feature requests to a cohesive, outcome-driven roadmap that aligns stakeholders, sequences work logically, and communicates strategic intent—avoiding "feature factory" roadmaps that lack strategic narrative or customer-centric framing. type: workflow theme: strategy-positioning best_for:

  • "Building a strategic roadmap that survives exec review"
  • "Prioritizing competing initiatives across multiple teams"
  • "Planning and sequencing work for the next quarter or half-year" scenarios:
  • "I have 15 competing initiatives and need to build a Q2 roadmap my exec team will actually approve"
  • "I'm planning our 6-month product roadmap and need to sequence work across 3 teams" estimated_time: "45-90 min"

Purpose

Guide product managers through strategic roadmap planning by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing skills into a structured process. Use this to move from disconnected feature requests to a cohesive, outcome-driven roadmap that aligns stakeholders, sequences work logically, and communicates strategic intent—avoiding "feature factory" roadmaps that lack strategic narrative or customer-centric framing.

This is not a Gantt chart—it's a strategic communication tool that shows what you're building, why it matters, and how it ladders up to business outcomes.

Input

Works best with: The product and planning horizon (next quarter, next year). Also useful: Strategy or OKRs to ladder to, the candidate initiative list, team capacity, and known stakeholder pressures.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. The workflow starts by establishing strategic context, then moves through prioritization, epic definition, and sequencing.

Example invocation: Plan a 2-quarter roadmap for our mobile app: here are our 3 OKRs and a list of 12 candidate initiatives.

Key Concepts

What is Strategic Roadmap Planning?

Roadmap planning is the process of:

  1. Gathering inputs — Customer problems, business goals, technical constraints
  2. Defining initiatives — Epics with clear hypotheses and success metrics
  3. Prioritizing — Rank initiatives by impact, effort, strategic fit
  4. Sequencing — Organize into releases/quarters with logical dependencies
  5. Communicating — Present roadmap to stakeholders with strategic narrative

Types of Roadmaps

Now/Next/Later Roadmap:

  • Now: Current quarter (committed)
  • Next: Following quarter (high confidence)
  • Later: Future exploration (low confidence)
  • Best for: Agile teams, uncertainty, continuous discovery

Theme-Based Roadmap:

  • Organize by strategic themes (e.g., "Retention," "Enterprise Expansion," "Mobile Experience")
  • Best for: Communicating to execs, showing strategic intent

Timeline Roadmap (Quarters):

  • Q1: Epics A, B; Q2: Epics C, D; Q3: Epics E, F
  • Best for: Resource planning, stakeholder communication

Feature-Based Roadmap (Anti-Pattern):

  • Lists features without context (e.g., "Dark mode," "SSO," "Advanced reporting")
  • Why it fails: No strategic narrative, no customer problems framed

Why This Works

  • Outcome-driven: Ties initiatives to business/customer outcomes
  • Stakeholder alignment: Transparent process reduces political friction
  • Strategic clarity: Shows not just "what" but "why"
  • Flexible: Adapts as you learn from discovery/delivery

Anti-Patterns (What This Is NOT)

  • Not a commitment: Roadmaps are strategic plans, not contracts
  • Not a feature list: Roadmaps frame problems, not just solutions
  • Not waterfall: Roadmaps evolve quarterly based on learning

When to Use This

  • Annual or quarterly planning cycles
  • After product strategy session (translate strategy to roadmap)
  • Onboarding new stakeholders (align on direction)
  • Reframing existing roadmap (shift from feature-driven to outcome-driven)

When NOT to Use This

  • For tactical sprint planning (use backlog instead)
  • When strategy is unclear (run product-strategy-session first)
  • When stakeholders expect date commitments (address expectations first)

Facilitation Source of Truth

When running this workflow as a guided conversation, use workshop-facilitation as the interaction protocol.

It defines:

  • session heads-up + entry mode (Guided, Context dump, Best guess)
  • one-question turns with plain-language prompts
  • progress labels (for example, Context Qx/8 and Scoring Qx/5)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include Other (specify) when useful)

This file defines the workflow sequence and domain-specific outputs. If there is a conflict, follow this file's workflow logic.

Application

Use template.md for the full fill-in structure.

This workflow orchestrates 5 phases over 1-2 weeks, using multiple component and interactive skills.


Phase 1: Gather Inputs (Day 1-2)

Goal: Collect business goals, customer problems, technical constraints, stakeholder requests.

Activities

1. Review Business Goals (OKRs, Strategic Initiatives)

  • Source: Company OKRs, exec strategy memos, board decks
  • Questions:
    • What are the company's top 3 priorities this year?
    • What metrics must we move? (revenue, retention, acquisition, efficiency)
    • Are there strategic bets? (new markets, partnerships, product lines)
  • Output: 3-5 business outcomes to optimize for

2. Review Customer Problems (Discovery Insights)

  • Source: Discovery interviews, support tickets, NPS feedback, churn surveys
  • Use: Insights from skills/discovery-process/SKILL.md (if recently completed)
  • Questions:
    • What are the top 3-5 customer pain points?
    • Which problems affect the most customers?
    • Which problems have highest intensity?
  • Output: 3-5 validated customer problems

3. Review Technical Constraints & Opportunities

  • Source: Engineering leadership, tech debt assessments
  • Questions:
    • Are there technical blockers? (scaling, performance, security)
    • Are there enabling investments? (platform upgrades, API rewrites)
    • What's the technical roadmap? (migrations, deprecations)
  • Output: List of technical investments required

4. Review Stakeholder Requests

  • Source: Sales, marketing, customer success, execs
  • Questions:
    • What are sales asking for? (enterprise features, integrations)
    • What's marketing requesting? (growth initiatives, positioning)
    • What's customer success flagging? (churn risks, expansion blockers)
  • Output: List of stakeholder requests (not yet committed)

Outputs from Phase 1

  • Business outcomes: 3-5 OKRs or strategic goals
  • Customer problems: 3-5 validated pain points
  • Technical investments: Platform/tech debt items
  • Stakeholder requests: Feature requests from internal teams

Phase 2: Define Initiatives (Epics) (Day 3-4)

Goal: Turn inputs into epics with hypotheses, success metrics, and effort estimates.

Activities

1. Define Epic Hypotheses

  • Use: skills/epic-hypothesis/SKILL.md (component)
  • For each initiative: Write hypothesis statement
  • Format: "We believe that [building X] for [persona] will achieve [outcome] because [assumption]."
  • Participants: PM
  • Duration: 60 minutes per epic
  • Output: 10-15 epic hypotheses

Example Epics (SaaS Product):

Epic 1: Guided Onboarding
Hypothesis: We believe that adding a step-by-step onboarding checklist for non-technical users will increase activation rate from 40% to 60% because users currently drop off due to lack of guidance.

Success Metric: Activation rate (% completing first action within 24 hours)
Target: 40% → 60%

Epic 2: Enterprise SSO
Hypothesis: We believe that adding SSO for enterprise accounts will increase enterprise deals closed from 2/quarter to 5/quarter because enterprise buyers require SSO for security compliance.

Success Metric: Enterprise deals closed per quarter
Target: 2 → 5

Epic 3: Mobile-Optimized Workflows
Hypothesis: We believe that optimizing core workflows for mobile will increase mobile DAU from 5% to 20% because mobile-first users currently can't complete workflows on the go.

Success Metric: Mobile DAU as % of total DAU
Target: 5% → 20%

2. Estimate Effort (T-Shirt Sizing)

  • Participants: PM + engineering lead
  • Duration: 90 minutes
  • Method:
    • Small (S): 1-2 weeks (1-2 engineers)
    • Medium (M): 3-4 weeks (2-3 engineers)
    • Large (L): 2-3 months (3-5 engineers)
    • Extra Large (XL): 3+ months (5+ engineers)
  • Output: Effort estimate per epic

3. Map to Business Outcomes

  • For each epic: Tag with primary business outcome
  • Example:
    • Epic 1 (Guided Onboarding) → Retention
    • Epic 2 (Enterprise SSO) → Acquisition (enterprise)
    • Epic 3 (Mobile Workflows) → Engagement

Outputs from Phase 2

  • 10-15 epics: Each with hypothesis, success metric, effort estimate
  • Business outcome mapping: Which epics drive which OKRs

Phase 3: Prioritize Initiatives (Day 5)

Goal: Rank epics by impact, effort, and strategic fit.

Activities

1. Choose Prioritization Framework

  • Use: skills/prioritization-advisor/SKILL.md (interactive)
  • Participants: PM
  • Duration: 30 minutes
  • Output: Recommended framework (RICE, ICE, Value/Effort, etc.)

2. Score Epics

  • Participants: PM, engineering lead, product leadership
  • Duration: 120 minutes
  • Method: Apply framework to all epics
  • Example (RICE scoring):

| Epic | Reach | Impact | Confidence | Effort | RICE Score | |------|-------|--------|------------|--------|------------| | Guided Onboarding | 10,000 users | 3 (massive) | 80% | 1 month | 24,000 | | Enterprise SSO | 500 users | 3 (massive) | 90% | 2 months | 675 | | Mobile Workflows | 5,000 users | 2 (high) | 60% | 3 months | 2,000 | | Advanced Reporting | 2,000 users | 2 (high) | 50% | 2 months | 1,000 |

3. Adjust for Strategic Fit

  • Review scores: Do they align with business goals?
  • Strategic overrides: Promote epics that align with strategic bets (even if score is lower)
  • Example: Enterprise SSO scores lower, but it's critical for enterprise expansion strategy → boost priority

Outputs from Phase 3

  • Ranked backlog: Epics sorted by priority (RICE score + strategic adjustments)
  • Top 10 epics: Highest-priority initiatives for roadmap

Phase 4: Sequence Roadmap (Day 6-7)

Goal: Organize epics into quarters/releases with logical dependencies.

Activities

1. Map Dependencies

  • Questions:
    • Does Epic B depend on Epic A? (e.g., "Advanced Reporting" requires "Data Pipeline Upgrade")
    • Are there technical blockers? (e.g., "Mobile App" requires "API Redesign")
  • Output: Dependency graph (Epic A → Epic B → Epic C)

2. Sequence by Quarter (or Release)

  • Now (Q1): Top 3-5 epics, no dependencies
  • Next (Q2): Next 3-5 epics, may depend on Q1 completion
  • Later (Q3+): Remaining epics, lower confidence

Example Roadmap (Timeline-Based):

Q1 2026 (Now - Committed):
├─ Guided Onboarding (Re

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryProduct
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium