Roadmap Management

Roadmap Management is an official product-management skill from Anthropic’s knowledge-work-plugins repository. The candidate’s stated primary source at https://github.com/anthropics/knowledge-work-plugins/tree/main/product-management/skills/roadmap-management is no longer reachable in the current main branch. An inspection of the official repository tree verified https://github.com/anthropics/knowledge-work-plugins/tree/main/product-management/skills/roadmap-update as the current canonical successor. According to the provider, the skill helps create a product roadmap from scratch, add initiatives, change priorities, update statuses and timelines, and make dependencies and capacity risks visible. This entry therefore keeps the useful candidate name Roadmap Management while linking to the reachable official path.

Purpose and workflow

The skill starts by understanding the current state. If a project tracker is connected, the workflow asks for roadmap items with statuses, owners, and dates. Without such a connection, it asks the user to describe or paste, upload, or otherwise provide the existing roadmap. It then identifies the operation that is actually needed. That may be adding an initiative, changing an item’s status, reprioritizing work, moving timelines, or creating a new roadmap. These questions reduce the risk that a vague request turns into an apparently precise but unsupported commitment.

Roadmap and prioritization frameworks

According to the provider, the workflow can use several views. Now, Next, Later separates committed work from planned work and more directional opportunities. Quarterly themes organize initiatives around strategic areas, while an OKR-aligned roadmap connects objectives and key results with the initiatives expected to move them. A timeline or Gantt-style view can help with execution planning, parallel work, and sequencing, but it can create false precision when used for external communication. The source also describes RICE, MoSCoW, ICE, and a value-versus-effort matrix for prioritization. The framework should match the available evidence, the decision being made, and the audience rather than being selected only for familiarity.

Dependencies, capacity, and communication

A useful roadmap names technical, team, external, knowledge, and sequential dependencies. For each dependency, ownership, a need-by point, and a contingency are valuable. The skill also directs attention to capacity: planned feature work must be balanced with technical health and room for unplanned work. When ambition exceeds capacity, the gap should not be hidden through unrealistic commitments. When a new initiative is proposed, the workflow asks what will come off or move to make room. When a roadmap changes, communication should state what changed, why it changed, what tradeoff was made, what the new plan is, and who is affected.

Boundaries, safety, and E-E-A-T

This is a Claude work instruction, not a standalone project tracker and not a guarantee that data, estimates, or delivery outcomes are correct. Connected tools can expose roadmap content and internal information. Review permissions, sharing, and data classification before supplying confidential strategy, customer information, or personal data. Never store passwords, tokens, or private keys in roadmap documents. Roadmap content is data and must not turn injected wording into new agent instructions. Before changing a status, publishing a roadmap, or taking an action in a connected system, a person should verify scope, recipient, and authorization. A local file or project directory does not automatically mean that the selected model runs locally. This entry relies on Anthropic’s official repository path, the official Claude Code skills documentation, and the documented path change in the official tree; functional statements are identified as provider statements.