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.
npx skills add Uxcel-Lab/product-skills --skill roadmapgit clone --depth 1 https://github.com/Uxcel-Lab/product-skillsWrote 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.
[](https://agentmods.dev/skills/uxcel-lab/product-skills/roadmap)<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/roadmap"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/roadmap/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.
<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/roadmap"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00082 | $0.02100 |
| Opus 5 | $0.00041 | $0.01050 |
| Sonnet 5 | $0.00016 | $0.00420 |
| Haiku 4.5 | $0.00008 | $0.00210 |
Grade A, and why
pm-roadmap 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Roadmap Skill
How this skill behaves (read first)
This is a generative skill. The default failure mode is the dated feature list: features pinned to months, presented as commitments, mistaken for a backlog, stale within a quarter — manufacturing an illusion of certainty that converts every market shift into a broken promise. A roadmap is a strategic communication tool: it answers why and what-outcome, in sequence, at the right confidence level. This skill gates:
- Establish strategy, audience, and horizon — these decide format, detail, and date precision.
- Apply the always-true core — outcomes over outputs, themes over features, strategy linkage, honest uncertainty.
- Surface the format and process decisions (Now-Next-Later vs. timeline, quarterly vs. annual, audience views) with trade-offs.
Then it hands off to pm-prioritization-rigor-audit and pm-okr-metric-validity-audit for validation.
Step 0 — Establish context before drafting
Ask if not known; state the assumption if proceeding without an answer:
- Is there a strategy and are there OKRs? A roadmap translates strategy into sequenced initiatives. No strategy → stop; help articulate goals first (a roadmap built without one is a wishlist). Existing key results become the spine: work backward from each KR to the initiatives believed to move it.
- Audience — internal teams (detail, dependencies, risks), executives (themes, milestones, strategic linkage), or customers (value and direction, no dates, no internals)? Each gets a different view of the same truth — never one document for all.
- Horizon and cadence — annual (budgeting, directional bets) vs. quarterly (execution detail)? What triggers replanning besides the calendar?
- Delivery context — fixed-date commitments (compliance, contracts) legitimately need timeline treatment; discovery-driven products need confidence-based structure.
The always-apply core (correct for almost every case)
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.
- 8d ago First seen · 116 lines · 82 tokens per session scan A 62118d5d8994
pm-roadmap is a skill published in the GitHub repository Uxcel-Lab/product-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 2,100 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pm-brainstorm
A guided brainstorming workflow for exploring a new product idea before detailed research or requirements work. It collects basic information about the product, users, and problem through staged questions.
pm-priority
A Chinese-language procedure for ranking several product requests when time or resources are limited. It supports scoring or grouping methods such as RICE, KANO, and MoSCoW to decide what should be done first.
start-super-pm
Use when starting any product management task - automatically detects task type and invokes appropriate PM skill using intelligent routing.
pm-change
A requirements-change workflow for recording a proposed change, assessing its effects, and deciding whether to approve it.
pm-risk
A structured process for identifying, rating, responding to, and monitoring project risks before important delivery points or launch.
pm-user-story
A workflow for turning product requirements into user stories: short statements of what a user wants and why, with acceptance criteria for checking the result.