nexus: Command for Claude Code

.claude/commands/agent-os/plan-product.md

plan-product is a command for Claude Code from adawalli/nexus. It costs 0 tokens per session (356 once invoked), scanned A, original, MIT.

A command that documents a product's purpose, users, planned development stages, and chosen technologies. It creates these plans as files in the project's agent-os/product directory.

In plain words
What is it for?
Use it to plan a product, identify its users and features, define its mission, create a roadmap, and record its technology stack. A roadmap is a staged plan for what to build over time.
Why use it?
It gives a project a shared direction before feature work begins. This helps keep product goals, the development roadmap, and technology choices in one place.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is adawalli/nexus's own configuration. It tells Claude Code how to work on nexus itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything nexus configures →

Reuse

Borrowing it

Nothing to install: this file belongs to adawalli/nexus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/adawalli/nexus/main/.claude/commands/agent-os/plan-product.md
Clone the repo
git clone --depth 1 https://github.com/adawalli/nexus

Made for: Claude Code.

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/adawalli/nexus/plan-product/github.svg)](https://agentmods.dev/commands/adawalli/nexus/plan-product)
Your own site
<a href="https://agentmods.dev/commands/adawalli/nexus/plan-product"><img src="https://agentmods.dev/badge/commands/adawalli/nexus/plan-product/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.

agentmods 80×15 button for plan-product

Your own site · 80×15
<a href="https://agentmods.dev/commands/adawalli/nexus/plan-product"><img src="https://agentmods.dev/badge/commands/adawalli/nexus/plan-product.svg" alt="Reviewed on agentmods" width="80" 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 356 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00356
Opus 5.5 $0.00000 $0.00142
Sonnet 5.5 $0.00000 $0.00071
Haiku 4.5 $0.00000 $0.00036

Measured 2mo ago against content hash 3bd49770a44b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

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

What it actually says

Product Planning Process

You are helping to plan and document the mission, roadmap and tech stack for the current product. This will include:

  • Gathering Information: The user's product vision, user personas, problems and key features
  • Mission Document: Take what you've gathered and create a concise mission document
  • Roadmap: Create a phased development plan with prioritized features
  • Tech stack: Establish the technical stack used for all aspects of this product's codebase

This process will create these files in agent-os/product/ directory.

PHASE 1: Gather Product Requirements

Use the product-planner subagent to create comprehensive product documentation.

IF the user has provided any details in regards to the product idea, its purpose, features list, target users and any other details then provide those to the product-planner subagent.

The product-planner will:

  • Confirm (or gather) product idea, features, target users, confirm the tech stack and gather other details
  • Create agent-os/product/mission.md with product vision and strategy
  • Create agent-os/product/roadmap.md with phased development plan
  • Create agent-os/product/tech-stack.md documenting all of this product's tech stack choices

PHASE 2: Inform the user

After all steps are complete, output the following to inform the user:

Your product planning is all set!

✅ Product mission: `agent-os/product/mission.md`
✅ Product roadmap: `agent-os/product/roadmap.md`
✅ Product tech stack: `agent-os/product/tech-stack.md`

NEXT STEP 👉 Run `/shape-spec` or `/write-spec` to start work on a feature!
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. 2mo ago First seen · 38 lines · 0 tokens per session scan A 3bd49770a44b

Subscribe to this mod's changes

plan-product is a command published in the GitHub repository adawalli/nexus (21 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 356 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-30.

Related

plan-product compared with commands from other repositories

plan-product next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
plan-productadawalli/nexusCommand2116d agoMITA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code