Borrowing it
Nothing to install: this file belongs to VGrss/Acumen. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/VGrss/Acumen/main/.agents/skills/roadmap/SKILL.mdgit clone --depth 1 https://github.com/VGrss/AcumenWrote 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/vgrss/acumen/roadmap)<a href="https://agentmods.dev/skills/vgrss/acumen/roadmap"><img src="https://agentmods.dev/badge/skills/vgrss/acumen/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/vgrss/acumen/roadmap"><img src="https://agentmods.dev/badge/skills/vgrss/acumen/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.00039 | $0.01093 |
| Opus 5.5 | $0.00016 | $0.00437 |
| Sonnet 5.5 | $0.00008 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
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 2mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap
Preparation
Before anything else, invoke /product-thinking to load strategic context, user segments, and product landscape. A roadmap disconnected from strategy is a feature list with dates.
Context Pull
Read .acumen/features.md for the current product landscape and known gaps. Read .acumen/competitors.md for competitive pressure and timing considerations. Read .acumen/value-chain.md for the end-to-end workflow per persona — sequence bets by which chain steps to strengthen or extend. Sequence bets against all three — value chain coverage, internal capability gaps, and external market pressure.
Mindset
A roadmap is a sequence of bets with sequencing logic. Not a Gantt chart. Not a promise. Not a list of features sorted by t-shirt size. Every increment ships a complete user outcome — if the next increment never ships, the previous one still delivered value. No technical-layer slicing. No "phase 1: build the API."
Core Reflex
- Organize by strategic themes — each theme ties to a user outcome and a business lever
- State the bet — for each theme, what are we betting will be true?
- Sequence by what unlocks what — dependencies and compounding value, not calendar quarters
- Break into vertical slices — each increment delivers end-to-end value a user can experience
Key Heuristics
Every increment must be valuable standalone
If the next increment never ships, does the current one still matter? If not, you sliced wrong. This is the single most important test. It forces honest prioritization and protects against half-built systems that deliver nothing.
Sequence by dependencies, not calendar
"Q2" is not a sequencing rationale. What unlocks what? Which bets generate learning that de-risks later bets? Which capabilities compound? Ship the thing that teaches you the most first.
"What we're NOT doing" is required
A roadmap without explicit exclusions is a wish list. State what you're choosing not to do and why. This forces the hard tradeoffs and prevents scope creep through ambiguity. If stakeholders can't see what was cut, they'll assume everything fits.
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.
- 2mo ago First seen · 93 lines · 39 tokens per session scan A 2b5b9bb87a31
roadmap is a skill published in the GitHub repository VGrss/Acumen (12 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,093 once invoked, about $0.0002 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-08-30.
roadmap compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| roadmapVGrss/Acumen | Skill | 12 | 3mo ago | Apache-2.0 | A | 39 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |