roadmap-management

roadmap-management is a skill for Claude Code from fergupa/claude_plugins. It costs 58 tokens per session (1,884 once invoked), scanned A, a copy of roadmap-management, Apache-2.0.

A product-roadmap planning tool for deciding which features and projects a team should work on and when. It supports common prioritization methods such as RICE, MoSCoW, and ICE, which are ways to compare expected value, effort, and urgency.

In plain words
What is it for?
Use it to create or reprioritize roadmaps, organize work into Now/Next/Later or quarters, map dependencies, and present planning decisions.
Why use it?
It helps teams make visible, consistent choices when there are more requests than time. It also makes dependencies and tradeoffs easier to explain to stakeholders.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the product-management plugin — 5 skills, 5 commands shipped together

Good fit Use it to create or reprioritize roadmaps, organize work into Now/Next/Later or quarters, map dependencies, and present planning decisions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fergupa/claude_plugins/roadmap-management
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add fergupa/claude_plugins --skill roadmap-management
Clone the repo
git clone --depth 1 https://github.com/fergupa/claude_plugins

Made for: Claude Code.

Or install product-management, the plugin that ships this one along with the rest of its 5 skills, 5 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for roadmap-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/fergupa/claude_plugins/roadmap-management/github.svg)](https://agentmods.dev/skills/fergupa/claude_plugins/roadmap-management)
Your own site
<a href="https://agentmods.dev/skills/fergupa/claude_plugins/roadmap-management"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/roadmap-management/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for roadmap-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/fergupa/claude_plugins/roadmap-management"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/roadmap-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,884 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.01884
Opus 5.5 $0.00023 $0.00754
Sonnet 5.5 $0.00012 $0.00377
Haiku 4.5 $0.00006 $0.00188

Measured 1mo ago against content hash 4f7355b580f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

roadmap-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to roadmap-management — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

product-management/skills/roadmap-management/SKILL.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Roadmap Management Skill

You are an expert at product roadmap planning, prioritization, and communication. You help product managers build roadmaps that are strategic, realistic, and useful for decision-making.

Roadmap Frameworks

Now / Next / Later

The simplest and often most effective roadmap format:

  • Now (current sprint/month): Committed work. High confidence in scope and timeline. These are the things the team is actively building.
  • Next (next 1-3 months): Planned work. Good confidence in what, less confidence in exactly when. Scoped and prioritized but not yet started.
  • Later (3-6+ months): Directional. These are strategic bets and opportunities we intend to pursue, but scope and timing are flexible.

When to use: Most teams, most of the time. Especially good for communicating externally or to leadership because it avoids false precision on dates.

Quarterly Themes

Organize the roadmap around 2-3 themes per quarter:

  • Each theme represents a strategic area of investment (e.g., "Enterprise readiness", "Activation improvements", "Platform extensibility")
  • Under each theme, list the specific initiatives planned
  • Themes should map to company or team OKRs
  • This format makes it easy to explain WHY you are building what you are building

When to use: When you need to show strategic alignment. Good for planning meetings and executive communication.

OKR-Aligned Roadmap

Map roadmap items directly to Objectives and Key Results:

  • Start with the team's OKRs for the period
  • Under each Key Result, list the initiatives that will move that metric
  • Include the expected impact of each initiative on the Key Result
  • This creates clear accountability between what you build and what you measure

When to use: Organizations that run on OKRs. Good for ensuring every initiative has a clear "why" tied to measurable outcomes.

Timeline / Gantt View

Calendar-based view with items on a timeline:

  • Shows start dates, end dates, and durations
  • Visualizes parallelism and sequencing
  • Good for identifying resource conflicts
  • Shows dependencies between items

Read the full file on GitHub · 169 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 169 lines · 58 tokens per session scan A 4f7355b580f7

Subscribe to this mod's changes

roadmap-management is a skill published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,884 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to roadmap-management, differing in 0 lines, and is treated as a copy.