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 rampstackco/claude-skills --skill roadmap-planninggit clone --depth 1 https://github.com/rampstackco/claude-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/rampstackco/claude-skills/roadmap-planning)<a href="https://agentmods.dev/skills/rampstackco/claude-skills/roadmap-planning"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/roadmap-planning/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/rampstackco/claude-skills/roadmap-planning"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/roadmap-planning.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.00111 | $0.02462 |
| Opus 5.5 | $0.00044 | $0.00985 |
| Sonnet 5.5 | $0.00022 | $0.00492 |
| Haiku 4.5 | $0.00011 | $0.00246 |
Grade A, and why
roadmap-planning 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- roadmap-planning — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Planning
Take a pile of ideas, requests, and ongoing work. Produce a defensible plan for what to ship, when, and why. The output is a roadmap document plus the prioritization work that made it credible.
When to use
- Planning the next quarter or the next year
- Sequencing work where some items depend on others
- Balancing new builds, improvements, and maintenance
- Saying no (or "not yet") to specific requests with a defensible reason
- Aligning a team around a single shared plan
- Communicating the plan to stakeholders outside the team
- Replanning after a strategy shift, a missed quarter, or new constraints
When NOT to use
- Specifying a single feature for development (use
pm-spec-writing) - Validating whether the idea is worth building (use
ux-research) - Designing the feature itself (use
design-standards) - Writing the launch plan for a single initiative (use
launch-runbook) - Reviewing what shipped vs what was promised (use
after-action-report)
Required inputs
- The team's strategy or top-level goals (1 to 5 OKRs, themes, or pillars)
- The backlog: every candidate item, with at least a one-sentence description
- The team's capacity (people × time)
- Known constraints (deadlines, dependencies, hiring, budget)
- The planning horizon (a quarter, two quarters, a year)
If the strategy is missing, the roadmap will be a list of features, not a plan. Push back and get the strategy first. A roadmap without strategy is just a queue.
The framework: 5 layers
Roadmaps fail at five different layers. A roadmap is only as good as its weakest one.
Layer 1: Themes (the WHY)
Top-level groupings tied to strategy. Every theme answers: "If we do nothing else this period, this is the outcome we want."
Good themes are:
- Outcome-shaped, not feature-shaped ("Reduce time-to-first-value" beats "Build onboarding")
- Limited (3 to 5 max)
- Defensible (you can explain why this and not something else)
- Measurable (each maps to one or two metrics)
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.
- 1mo ago First seen · 229 lines · 111 tokens per session scan A 136b637fe06e
roadmap-planning is a skill published in the GitHub repository rampstackco/claude-skills (995 stars, last pushed today), licensed MIT. It adds 111 tokens to every session and 2,462 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other skills, from other repositories
mass-ulw
Drives dependency-ordered child work through the native workflow tool, each phase's stages defined up front in one run, with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
crm-data-cleanup
Cleans up CRM data from HubSpot, Salesforce, Pipedrive, Zoho, Close, Attio, or any CRM CSV export. Finds duplicate contacts and companies with fuzzy matching (not just exact email), normalizes emails, phones to E.164, names, domains, states, and countries, flags stale, invalid, role, and test records, finds broken…
multi-agent-client-onboarding
Uses Agent SDK to deploy 3 parallel agents for client onboarding -- workflow auditor, tech stack mapper, and strategy drafter. Real consulting workflow that produces a complete client assessment.
meeting-intelligence
Analyze meeting transcripts to extract decisions, action items, blockers, sentiment, and generate follow-up emails. Use when user provides meeting notes, transcripts, or recordings and needs structured summaries or action tracking.
session-handoff
Use when a working session is ending, the context window is nearly full, work needs to pass to a teammate or a fresh session, or the user says "hand this off", "write this up before we lose it", "I'm starting a new session", or "summarize where we are". Produces a handoff document that lets the next session resume…
cross-conversation-project-manager
Maintain project state across MULTIPLE conversations over days/weeks. Track tasks, decisions, blockers, resources. Auto-update when project mentioned. Generate status reports and proactive reminders.