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 cwinvestments/memstack --skill roadmap-buildergit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/roadmap-builder)<a href="https://agentmods.dev/skills/cwinvestments/memstack/roadmap-builder"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/roadmap-builder/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/cwinvestments/memstack/roadmap-builder"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/roadmap-builder.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.00067 | $0.02706 |
| Opus 5.5 | $0.00027 | $0.01082 |
| Sonnet 5.5 | $0.00013 | $0.00541 |
| Haiku 4.5 | $0.00007 | $0.00271 |
Grade A, and why
memstack-product-roadmap-builder 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.
How it starts
The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Builder: Building product roadmap...
Creates a strategic product roadmap in Now/Next/Later format with quarterly themes, milestones, dependency mapping, resource allocation, and stakeholder communication templates.
Activation
When this skill activates, output:
Roadmap Builder: Building product roadmap...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User says "roadmap", "product roadmap", "quarterly plan" | ACTIVE |
| User says "now/next/later" or "OKRs" | ACTIVE |
| User wants to plan product direction for 3-12 months | ACTIVE |
| User wants to scope an MVP | DORMANT: use MVP Scoper |
| User wants sprint-level stories | DORMANT: use User Story Generator |
Common Mistakes
| Mistake | Why It's Wrong |
|---|---|
| "Roadmap with exact delivery dates" | Dates become promises. Use time horizons (Now/Next/Later) to preserve flexibility. |
| "Feature list disguised as a roadmap" | Roadmaps communicate outcomes and themes, not feature checklists. |
| "One roadmap for everyone" | Engineering, sales, and executives need different views of the same plan. |
| "Plan 12 months in detail" | Detailed plans beyond 3 months are fiction. Be specific for Now, directional for Later. |
| "Set it and forget it" | Roadmaps are living documents. Review and adjust monthly or quarterly. |
Protocol
Step 1: Gather Strategic Context
If the user hasn't provided details, ask:
- Product: what product are you roadmapping?
- Current state: what's been built? What's the current version?
- Company goals: what's the business trying to achieve this year?
- User feedback: what are the top 5 user requests or complaints?
- Competitive pressure: what are competitors shipping that matters?
- Resources: team size, key constraints, upcoming changes?
Step 2: Define Strategic Themes
Themes are the "why" behind your roadmap: outcomes, not features.
Theme template:
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 Changed 78989a11fc22
- 1mo ago First seen · 319 lines · 67 tokens per session scan A 908af9b0eb97
memstack-product-roadmap-builder is a skill published in the GitHub repository cwinvestments/memstack (425 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 2,706 once invoked, about $0.0003 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
ccpm
CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync…
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
nx
Best practices for Nx monorepo development, project configuration, and code generation.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.