Update, create, or reprioritize a product roadmap with clear priorities and timelines.
The material indicates this is essentially a prompt-based skill for roadmap updates, with no declared secrets, remote endpoints, or local execution capability, so overall risk is low. The main caveats are that it may process user-provided planning content and that community adoption and maintenance signals are limited.
The material explicitly states that no keys or environment variables are required, and there is no indication that users must provide API tokens, account passwords, or other sensitive credentials, so credential exposure risk is low.
No remote endpoint host is declared. The README only describes pulling roadmap information if a project tool is already connected, but the current material does not show this skill itself sending data to external services.
The system flags it as prompt-only, and the material does not describe starting local processes, running scripts, installing dependencies, or invoking system commands, so code execution exposure appears minimal.
This skill may process roadmap items, statuses, owners, dates, and dependencies supplied by the user or from a connected project tool. This is within normal functional scope, but it can involve internal planning data, so users should be mindful of sensitive content.
The source is the open GitHub repository anthropics/knowledge-work-plugins, which is a positive auditability signal. However, the license is unspecified, stars are 0, and maintenance status is unknown, so supply-chain maturity signals are limited and the repository contents and update status should be reviewed before adoption.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "roadmap-update" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/product-management/skills/roadmap-update/SKILL.md 2. Save it as ~/.claude/skills/roadmap-update/SKILL.md 3. Reload skills and tell me it's ready
Please add “team permission management” to our product roadmap for next quarter and assess which existing initiatives should be delayed or deprioritized. Current initiatives: mobile redesign, payment optimization, and user tagging system. Output the revised priorities, rationale, and suggested timeline.
A revised roadmap recommendation with the new initiative, priority changes, tradeoff rationale, and timeline.
We just learned that enterprise demand for audit logs is much stronger than expected. Reprioritize the product roadmap based on this information. Explain which initiatives should move up, which should move back, and provide a short leadership-facing summary.
An updated roadmap based on the new information, with clear explanations of priority shifts.
Please build a Now/Next/Later roadmap for a SaaS product using these candidate initiatives: single sign-on, usage analytics dashboard, API rate limiting, report export, mobile responsiveness, and ticketing integration. Classify them by business impact, implementation complexity, and dependencies, and briefly explain why.
A structured Now/Next/Later roadmap with classification logic and brief explanations.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Update, create, or reprioritize a product roadmap.
/roadmap-update $ARGUMENTS
If ~~project tracker is connected:
If no project management tool is connected:
Ask what the user wants to do:
Add item: New feature, initiative, or work item to the roadmap
Update status: Change status of existing items
Reprioritize: Change the order or priority of items
Move timeline: Shift dates for items
Create new roadmap: Build a roadmap from scratch
Produce a roadmap view with:
Quick summary: X items in progress, Y completed this period, Z at risk.
For each item, show:
Group items by:
If this is an update to an existing roadmap, summarize what changed:
After generating the roadmap:
The simplest and often most effective roadmap format:
When to use: Most teams, most of the time. Especially good for communicating externally or to leadership because it avoids false precision on dates.
Organize the roadmap around 2-3 themes per quarter:
…
Embed Zoom meeting features into web apps with full or component-based integration.
Build weighted sales forecasts with scenario planning, commit splits, and gap analysis.
Prepare compliant month-end journal entries with debits, credits, and support.
Analyze compensation bands, offer competitiveness, equity grants, and retention risks.
Track hiring stages, update candidate status, and monitor pipeline counts.
Research competitors and compare positioning, messaging, gaps, opportunities, and threats.
Create and edit project roadmaps in plain text for planning and alignment.
Create stakeholder updates tailored to audience, cadence, and communication goals.
Generate clear daily standup updates from recent commits, PRs, and ticket changes.
Plan artifact delivery routes to improve transport coordination and delivery efficiency.
Sync active tasks and refresh project memory to catch missed work.
Turn prototype feedback into traceable product decisions for team-wide alignment.