Borrowing it
Nothing to install: this file belongs to kamiazya/scopes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kamiazya/scopes/main/.claude/commands/pm/prd-new.mdgit clone --depth 1 https://github.com/kamiazya/scopesWrote 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/kamiazya/scopes/prd-new)<a href="https://agentmods.dev/commands/kamiazya/scopes/prd-new"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/prd-new/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.
<a href="https://agentmods.dev/commands/kamiazya/scopes/prd-new"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/prd-new.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01024 |
| Opus 5.5 | $0.00000 | $0.00410 |
| Sonnet 5.5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00102 |
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 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.
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.mdalready 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"
- Check if
-
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/"
- Check if
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
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.
- 2mo ago First seen · 149 lines · 0 tokens per session scan A d48fc60243b3
prd-new is a command published in the GitHub repository kamiazya/scopes (2 stars, last pushed 11mo 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.
prd-new compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| prd-newkamiazya/scopes | Command | 2 | 11mo ago | Apache-2.0 | A | 0 | Claude Code |
| diagnose-deeptracezscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 29 | Claude Code |
| troubleshoot-experiencezscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 25 | Claude Code |
| app-healthzscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 16 | Claude Code |
| compare-locationszscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 20 | Claude Code |
| investigate-alertszscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 23 | Claude Code |
| investigate-sandboxzscaler/zscaler-mcp-server | Command | 55 | 10d ago | MIT | A | 30 | Claude Code |