plan-product

plan-product is a command for Claude Code from peerjakobsen/smartspender. It costs 0 tokens per session (1,102 once invoked), scanned A, original, MIT.

An interactive command for creating basic product documentation: a mission, roadmap, and technology-stack description.

In plain words
What is it for?
It helps start or update files in agent-os/product/ through a guided conversation, while checking whether those documents already exist.
Why use it?
It turns a product discussion into a small set of shared documents, so the product's purpose and technical direction are recorded.

Command for Claude Code

Part of the smartspender plugin — 13 skills, 19 commands shipped together

Install

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.

agentmods
npx agentmods add commands/peerjakobsen/smartspender/plan-product
Clone the repo
git clone --depth 1 https://github.com/peerjakobsen/smartspender

Made for: Claude Code.

Or install smartspender, the plugin that ships this one along with the rest of its 13 skills, 19 commands.

Wrote 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.

agentmods badge for plan-product

README.md
[![agentmods](https://agentmods.dev/badge/commands/peerjakobsen/smartspender/plan-product.svg)](https://agentmods.dev/commands/peerjakobsen/smartspender/plan-product)
Your own site
<a href="https://agentmods.dev/commands/peerjakobsen/smartspender/plan-product"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/plan-product.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,102 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01102
Opus 5 $0.00000 $0.00551
Sonnet 5 $0.00000 $0.00220
Haiku 4.5 $0.00000 $0.00110

Measured 4d ago against content hash ecd1abef7c3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-product 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 4d 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.

.claude/commands/agent-os/plan-product.md · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan Product

Establish foundational product documentation through an interactive conversation. Creates mission, roadmap, and tech stack files in agent-os/product/.

Important Guidelines

  • Always use AskUserQuestion tool when asking the user anything
  • Keep it lightweight — gather enough to create useful docs without over-documenting
  • One question at a time — don't overwhelm with multiple questions

Process

Step 1: Check for Existing Product Docs

Check if agent-os/product/ exists and contains any of these files:

  • mission.md
  • roadmap.md
  • tech-stack.md

If any files exist, use AskUserQuestion:

I found existing product documentation:
- mission.md: [exists/missing]
- roadmap.md: [exists/missing]
- tech-stack.md: [exists/missing]

Would you like to:
1. Start fresh (replace all)
2. Update specific files
3. Cancel

(Choose 1, 2, or 3)

If option 2, ask which files to update and only gather info for those. If option 3, stop here.

If no files exist, proceed to Step 2.

Step 2: Gather Product Vision (for mission.md)

Use AskUserQuestion:

Let's define your product's mission.

**What problem does this product solve?**

(Describe the core problem or pain point you're addressing)

After they respond, use AskUserQuestion:

**Who is this product for?**

(Describe your target users or audience)

After they respond, use AskUserQuestion:

**What makes your solution unique?**

(What's the key differentiator or approach?)

Step 3: Gather Roadmap (for roadmap.md)

Use AskUserQuestion:

Now let's outline your development roadmap.

**What are the must-have features for launch (MVP)?**

(List the core features needed for the first usable version)

After they respond, use AskUserQuestion:

**What features are planned for after launch?**

(List features you'd like to add in future phases, or say "none yet")

Step 4: Establish Tech Stack (for tech-stack.md)

First, check if agent-os/standards/global/tech-stack.md exists.

Read the full file on GitHub · 205 lines

Changes

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.

  1. 4d ago First seen · 205 lines · 0 tokens per session scan A ecd1abef7c3b

Subscribe to this mod's changes

plan-product is a command published in the GitHub repository peerjakobsen/smartspender (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,102 tokens. 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.