agentmods.dev

agentcmd: Command for Claude Code

.claude/commands/cmd/generate-prd.md

generate-prd is a command for Claude Code from jnarowski/agentcmd. It costs 12 tokens per session (2,536 once invoked), scanned A, original, MIT.

A command that creates a product requirements document, or PRD: a high-level description of what a feature should do and why it matters. It saves the document in a dated project-specification folder.

In plain words
What is it for?
Use it to record feature context, user needs, and business value without yet defining coding tasks or complexity scores.
Why use it?
It separates product goals from implementation details before coding begins, giving later technical planning a clear starting point.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

This is jnarowski/agentcmd's own configuration. It tells Claude Code how to work on agentcmd 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 agentcmd configures →

not rated 18repo 10mo ago A scan 12 tokens original MIT
View source ↗ jnarowski/agentcmd agentcmd.dev
Reuse

Borrowing it

Nothing to install: this file belongs to jnarowski/agentcmd. 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/jnarowski/agentcmd/main/.claude/commands/cmd/generate-prd.md
Clone the repo
git clone --depth 1 https://github.com/jnarowski/agentcmd

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 generate-prd

README.md
[![agentmods](https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-prd/github.svg)](https://agentmods.dev/commands/jnarowski/agentcmd/generate-prd)
Your own site
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/generate-prd"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-prd/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 generate-prd

Your own site · 80×15
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/generate-prd"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,536 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.00012 $0.02536
Opus 5.5 $0.00005 $0.01014
Sonnet 5.5 $0.00002 $0.00507
Haiku 4.5 $0.00001 $0.00254

Measured 2mo ago against content hash 9737d99d6aae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

generate-prd 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/cmd/generate-prd.md · 312 lines

How it starts

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

Product Requirements Document (PRD)

Generate high-level PRD focusing on "what" and "why" before implementation. Creates folder at .agent/specs/todo/[id]-[feature]/prd.md with timestamp-based ID.

Variables

  • $param1: $1 (optional) - Feature context or description (infers from conversation if omitted)

Instructions

  • IMPORTANT: Use your reasoning model - THINK HARD about feature requirements, user needs, and business value
  • IMPORTANT: This command ONLY generates the PRD - do NOT implement any code or make file changes beyond creating the folder/file and updating index.json
  • Normalize feature name to kebab-case for the folder name
  • Replace ALL <placeholders> with specific details relevant to that section
  • Focus on WHAT and WHY, not HOW (save implementation details for spec)
  • Keep it high-level but comprehensive
  • DO NOT include implementation tasks or complexity scores - this is for planning only

Workflow

  1. Determine Context:

    • If $param1 provided: Use as context
    • If $param1 empty: Infer from conversation history

  2. Generate Spec ID:

    • Generate timestamp-based ID in format YYMMDDHHmm using current local time
    • Example: November 13, 2025 at 3:22pm local → 2511131522
    • Read .agent/specs/index.json (will be updated in step 8)

  3. Generate Feature Name:

    • Generate concise kebab-case name from context (max 4 words)
    • Examples: "Add OAuth support" → "oauth-support", "Dashboard redesign" → "dashboard-redesign"

  4. Research Phase:

    • Research codebase for existing patterns relevant to the feature
    • Gather context about architecture, file structure, and conventions
    • Look for similar features for inspiration

  5. Clarification (conditional):

    • If explicit context provided: Resolve ambiguities autonomously using recommended best practices
    • If inferring from conversation: Ask clarifying questions ONE AT A TIME if requirements are unclear:
      • Don't use the Question tool
      • Use this template:

Read the full file on GitHub · 312 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. 2mo ago First seen · 312 lines · 12 tokens per session scan A 9737d99d6aae

Subscribe to this mod's changes

generate-prd is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 12 tokens to every session and 2,536 once invoked, about $0.0000 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-01.

PlanningProject management
Related

generate-prd compared with commands from other repositories

generate-prd next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
generate-prdjnarowski/agentcmdCommand1810mo agoMITA12Claude 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