A command that starts brainstorming for a product requirements document, a written description of what a proposed feature should do.

It is for beginning a requirements document for a named feature. Feature names must use lowercase letters, numbers, and hyphens.

It gives a defined starting point for shaping a feature before development begins.

prd-new — Command for Claude Code by kamiazya: A command that starts brainstorming for a product requirements…

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/kamiazya/scopes/prd-new

Clone the repo

git clone --depth 1 https://github.com/kamiazya/scopes

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/kamiazya/scopes/prd-new.svg)](https://agentmods.dev/commands/kamiazya/scopes/prd-new)

Your own site

<a href="https://agentmods.dev/commands/kamiazya/scopes/prd-new"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/prd-new.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,024 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01024
Opus 5	$0.00000	$0.00512
Sonnet 5	$0.00000	$0.00205
Haiku 4.5	$0.00000	$0.00102

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

Security

Grade A, and why

prd-new 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/pm/prd-new.md · 149 lines

How it starts

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

PRD New

Launch brainstorming for new product requirement document.

Usage

/pm:prd-new <feature_name>

Required Rules

IMPORTANT: Before executing this command, read and follow:

.claude/rules/datetime.md - For getting real current date/time

Preflight Checklist

Before proceeding, complete these validation steps. Do not bother the user with preflight checks progress ("I'm not going to ..."). Just do them and move on.

Input Validation

Validate feature name format:
- Must contain only lowercase letters, numbers, and hyphens
- Must start with a letter
- No spaces or special characters allowed
- If invalid, tell user: "❌ Feature name must be kebab-case (lowercase letters, numbers, hyphens only). Examples: user-auth, payment-v2, notification-system"
Check for existing PRD:
- Check if .claude/prds/$ARGUMENTS.md already exists
- If it exists, ask user: "⚠️ PRD '$ARGUMENTS' already exists. Do you want to overwrite it? (yes/no)"
- Only proceed with explicit 'yes' confirmation
- If user says no, suggest: "Use a different name or run: /pm:prd-parse $ARGUMENTS to create an epic from the existing PRD"
Verify directory structure:
- Check if .claude/prds/ directory exists
- If not, create it first
- If unable to create, tell user: "❌ Cannot create PRD directory. Please manually create: .claude/prds/"

Instructions

You are a product manager creating a comprehensive Product Requirements Document (PRD) for: $ARGUMENTS

Follow this structured approach:

1. Discovery & Context

Ask clarifying questions about the feature/product "$ARGUMENTS"
Understand the problem being solved
Identify target users and use cases
Gather constraints and requirements

2. PRD Structure

Create a comprehensive PRD with these sections:

Executive Summary

Brief overview and value proposition

Problem Statement

What problem are we solving?
Why is this important now?

User Stories

Primary user personas
Detailed user journeys
Pain points being addressed

Read the full file on GitHub · 149 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.

4d ago First seen · 149 lines · 0 tokens per session scan A d48fc60243b3

Subscribe to this mod's changes

prd-new is a command published in the GitHub repository kamiazya/scopes (2 stars, last pushed 9mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,024 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.

Planning hacktoberfest mcp-server taskmanagement todoapp

prd-new