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 tikalk/adlc-team-skills --skill product-roadmapgit clone --depth 1 https://github.com/tikalk/adlc-team-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/tikalk/adlc-team-skills/product-roadmap)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/product-roadmap"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/product-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/tikalk/adlc-team-skills/product-roadmap"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/product-roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.03152 |
| Opus 5 | $0.00037 | $0.01576 |
| Sonnet 5 | $0.00015 | $0.00630 |
| Haiku 4.5 | $0.00007 | $0.00315 |
Grade A, and why
product-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 12d 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
product-roadmap
What this skill does
Tracks product milestone progress across four layers of truth — because "done" is a stronger claim than "tasks complete":
| Layer | Question | Source |
|---|---|---|
| Decision | Was the decision made/approved? | PDR status (Proposed → Accepted → Completed) |
| Execution | Was the work done? | Live issue states via MCP (GitHub / GitLab / Jira / Linear) |
| Evidence | Does the code actually show it? | Code-vs-PDR verification (init concept) |
| Gates | Was the bar cleared? | Milestone PDR gate table |
A milestone is live only when all four layers are green. Anything less gets a done-means warning.
When to use
- Weekly progress check
- Before release to verify milestone completion
- Quarterly roadmap review
- After closing issues to check if milestone can be promoted
When NOT to use
- No PDRs exist (use
/product-specifyor/product-initfirst) - You want to create PDRs (use
/product-specify)
Execution Steps
Phase A: Load PDRs
sh: scripts/bash/setup-product-roadmap.sh [--json]
ps: scripts/powershell/setup-product-roadmap.ps1
Read PDR files (memory first, drafts fallback):
{REPO_ROOT}/.adlc/memory/pdr/PDR-*.md(Accepted/Completed){REPO_ROOT}/.adlc/drafts/pdr/PDR-*.md(Proposed/Discovered)
Identify milestones: PDRs with Category: Milestone. These define the roadmap structure and contain the ### Gates table, ### Features Included table, ### Done Means definition, and optional ### Tracker Milestone URL.
Phase B: Issue State via MCP
Extract issue URLs from all PDRs — look for ### Issues sections containing full URLs.
Detect tracker from URL host:
| URL host | Tracker | MCP tool pattern |
|---|---|---|
github.com |
GitHub | github_* MCP tools |
gitlab.com |
GitLab | gitlab_* MCP tools |
*.atlassian.net |
Jira | jira_* MCP tools |
linear.app |
Linear | linear_* MCP tools |
Query issue states — for each issue URL, use the matching MCP tool to get state (open/closed/in-progress):
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 279 lines · 75 tokens per session scan A 1b66064c386e
product-roadmap is a skill published in the GitHub repository tikalk/adlc-team-skills (133 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 3,152 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-30.
Other skills, from other repositories
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
workspace
Dynamic multi-repo and monorepo awareness for Claude Code. Analyze workspace topology, track API contracts, and maintain cross-repo context.
ticket-craft
Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing.
team-coordination
Multi-person projects - shared state, todo claiming, handoffs.