Roadmap Update
Reprioritize what you ship next as a solo builder when a new idea, slip, or customer signal forces a tradeoff on your roadmap.
Overview
Roadmap Update is an agent skill most often used in Build (also Validate and Operate) that updates, creates, or reprioritizes a product roadmap with explicit tradeoffs when capacity or timelines change.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill roadmap-updateWhat is this skill?
- 7-step workflow from current-state pull through documented tradeoffs and delivery back to your tracker or doc
- Connector-aware intake: pulls roadmap items from a linked project tracker or accepts paste/upload in any format
- Four change modes: add item, update status (not started through cut), reprioritize order, and adjust timelines with depe
- Impact pass flags overdue/at-risk items, capacity conflicts, and what slips or gets cut before you commit
- Outputs structured diffs you can paste into Linear, Notion, Jira, or a Now/Next/Later doc without reformatting
- 7-step roadmap update workflow
- 4 roadmap operations: add item, update status, reprioritize, and adjust timelines
Adoption & trust: 1.6k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your priorities shifted but your roadmap is a stale list with no clear what moves, what slips, or what gets cut.
Who is it for?
Solo builders maintaining a single-product roadmap who need structured add/reprioritize/timeline operations and honest capacity tradeoffs in one session.
Skip if: Teams that already lock roadmap changes only in formal quarterly planning with no live tracker or doc to update, or when you only need a one-off feature spec with no sequencing across initiatives.
When should I use this skill?
Adding a new roadmap initiative and deciding what moves, shifting priorities after new information, moving timelines due to dependency slips, or building a Now/Next/Later view from scratch.
What do I get? / Deliverables
You leave with an updated ordered roadmap, documented tradeoffs, and paste-ready changes for your tracker or Now/Next/Later doc before you commit engineering time.
- Updated roadmap or Now/Next/Later view with ordered initiatives
- Change summary documenting tradeoffs, slips, cuts, and status updates
- Structured diffs ready to paste into your PM tool or shared doc
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Roadmap updates are the core product-management shelf in Build because they turn backlog and capacity into an ordered shipping plan your agent can maintain. The pm subphase is where initiative intake, sequencing, and owner/date hygiene belong—this skill’s workflow is built around those artifacts rather than code or marketing execution.
Where it fits
After a landing-page test, you add a validation initiative and reprioritize Build items so MVP scope still fits one-person capacity.
You insert a integration milestone, mark a dependency blocked, and reorder Next/Later before sprint planning with your coding agent.
Post-launch support load spikes so you shift timelines and cut a nice-to-have while keeping reliability work in Now.
A retention experiment wins so you promote a lifecycle feature on the roadmap and defer a distribution experiment to Later.
How it compares
Use instead of unstructured chat reprioritization when you want a repeatable PM workflow with impact checks, not a generic brainstorming session.
Common Questions / FAQ
Who is roadmap-update for?
It is for solo and indie product owners who own the shipping sequence and need an agent-guided way to mutate the roadmap without losing dependencies, owners, or rationale.
When should I use roadmap-update?
Use it when adding a new initiative and deciding what to defer, after new validation or customer signal changes priority, when a dependency slip forces timeline moves, or when you are creating a Now/Next/Later view from scratch. In Validate it helps rescope what enters Build; in
Is roadmap-update safe to install?
Treat it like any third-party agent skill: review the Security Audits panel on this Prism page and limit connected PM tools to accounts you trust before granting network or API access.
SKILL.md
READMESKILL.md - Roadmap Update
# Roadmap Update > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Update, create, or reprioritize a product roadmap. ## Usage ``` /roadmap-update $ARGUMENTS ``` ## Workflow ### 1. Understand Current State If **~~project tracker** is connected: - Pull current roadmap items with their statuses, assignees, and dates - Identify items that are overdue, at risk, or recently completed - Surface any items without clear owners or dates If no project management tool is connected: - Ask the user to describe their current roadmap or paste/upload it - Accept any format: list, table, spreadsheet, screenshot, or prose description ### 2. Determine the Operation Ask what the user wants to do: **Add item**: New feature, initiative, or work item to the roadmap - Gather: name, description, priority, estimated effort, target timeframe, owner, dependencies - Suggest where it fits based on current priorities and capacity **Update status**: Change status of existing items - Options: not started, in progress, at risk, blocked, completed, cut - For "at risk" or "blocked": ask for the blocker and mitigation plan **Reprioritize**: Change the order or priority of items - Ask what changed (new information, strategy shift, resource change, customer feedback) - Apply a prioritization framework if helpful — see **Prioritization Frameworks** below for RICE, MoSCoW, ICE, and value-vs-effort - Show before/after comparison **Move timeline**: Shift dates for items - Ask why (scope change, dependency slip, resource constraint) - Identify downstream impacts on dependent items - Flag items that move past hard deadlines **Create new roadmap**: Build a roadmap from scratch - Ask about timeframe (quarter, half, year) - Ask about format preference (Now/Next/Later, quarterly columns, OKR-aligned) — see **Roadmap Frameworks** below - Gather the list of initiatives to include ### 3. Generate Roadmap Summary Produce a roadmap view with: #### Status Overview Quick summary: X items in progress, Y completed this period, Z at risk. #### Roadmap Items For each item, show: - Name and one-line description - Status indicator (on track / at risk / blocked / completed / not started) - Target timeframe or date - Owner - Key dependencies Group items by: - Timeframe (Now / Next / Later) or quarter, depending on format - Or by theme/goal if the user prefers #### Risks and Dependencies - Items that are blocked or at risk, with details - Cross-team dependencies and their status - Items approaching hard deadlines #### Changes This Update If this is an update to an existing roadmap, summarize what changed: - Items added, removed, or reprioritized - Timeline shifts - Status changes ### 4. Follow Up After generating the roadmap: - Offer to format for a specific audience (executive summary, engineering detail, customer-facing) - Offer to draft communication about roadmap changes - If project management tool is connected, offer to update ticket statuses ## 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