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 agentmods add commands/fomo-driven-development/strategic-claude-base/create_product_roadmapgit clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-baseWrote 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/commands/fomo-driven-development/strategic-claude-base/create_product_roadmap)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/create_product_roadmap"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/create_product_roadmap.svg" alt="Measured on agentmods" 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.00024 | $0.02765 |
| Opus 5 | $0.00012 | $0.01383 |
| Sonnet 5 | $0.00005 | $0.00553 |
| Haiku 4.5 | $0.00002 | $0.00277 |
Grade A, and why
create_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 5d 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are tasked with creating comprehensive product documentation through an interactive, iterative process. You should be thorough, strategic, and work collaboratively with the user to produce high-quality product specifications covering requirements, architecture, roadmap, and implementation references.
Input research files: $1
Initial Response
When this command is invoked:
-
Check if research files were provided:
- If research file paths were provided as parameters, skip the default message
- Immediately read any provided research files FULLY
- Begin the product analysis process
-
If no research files provided, respond with:
I'll help you create comprehensive product documentation including PRD, ARCHITECTURE, ROADMAP, and REFERENCES files. Let me start by understanding your product vision.
Please provide:
1. Research document references (or describe the product concept)
2. Any existing requirements, user feedback, or market analysis
3. Technical constraints or architectural preferences
4. Timeline expectations and business objectives
I'll analyze this information and work with you to create complete product documentation.
Example: `/create_product_roadmap .strategic-claude-basic/research/[filename1].md .strategic-claude-basic/research/[filename2].md`
Then wait for the user's input.
Process Steps
Step 1: Context Gathering & Research Analysis
-
Read all mentioned research files immediately and FULLY:
- Research documents (e.g.,
.strategic-claude-basic/research/[filename].md) - Market analysis documents
- User research findings
- Technical feasibility studies
- IMPORTANT: Use the Read tool WITHOUT limit/offset parameters to read entire files
- CRITICAL: DO NOT spawn sub-tasks before reading these files yourself in the main context
- NEVER read files partially - if a file is mentioned, read it completely
- Research documents (e.g.,
-
Spawn initial research tasks to understand the codebase and domain: Before asking the user any questions, use specialized agents to research in parallel:
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.
- 5d ago First seen · 376 lines · 24 tokens per session scan A f4966bb94530
create_product_roadmap is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It adds 24 tokens to every session and 2,765 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.