A structured document for describing what a product or software feature should do, why it is needed, and who it serves. It covers users, requirements, success measures, user flows, and technical considerations.

Use it to plan a new product or feature, describe user needs, set measurable goals, organize requirements, and record technical constraints.

It turns a broad product idea into shared instructions for design and development. It helps expose missing decisions, define what is out of scope, and measure whether the result works.

prd — Command for coding agents by CrashBytes: A structured document for describing what a product or…

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/crashbytes/claude-role-skills/prd

Clone the repo

git clone --depth 1 https://github.com/CrashBytes/claude-role-skills

Or install role-based-skills, the plugin that ships this one along with the rest of its 7 skills, 15 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/prd.svg)](https://agentmods.dev/commands/crashbytes/claude-role-skills/prd)

Your own site

<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/prd"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/prd.svg" alt="Measured on agentmods" height="20"></a>

Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 382 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.00005	$0.00382
Opus 5	$0.00003	$0.00191
Sonnet 5	$0.00001	$0.00076
Haiku 4.5	$0.00001	$0.00038

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

Security

Grade A, and why

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 5d 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.

commands/prd.md · 68 lines

What it actually says

Product Requirements Document

Draft a structured PRD for a product or feature.

Arguments

Product or feature: $ARGUMENTS

Workflow

Gather context
- Parse the product/feature description
- If codebase is available, scan for existing implementation context
- Identify the target market and user segments
Draft PRD sections

Executive Summary
- One paragraph: what, why, and for whom
Problem Statement
- What pain point does this solve?
- How are users solving this today?
- What's the cost of not solving it?
Goals and Success Metrics
- 2-3 measurable goals
- Key metrics (AARRR: Acquisition, Activation, Retention, Revenue, Referral)
- Target values and measurement timeline
User Personas
- Primary and secondary personas
- Jobs to be done for each
Requirements
- Functional requirements (must-have, should-have, nice-to-have)
- Non-functional requirements (performance, security, scalability, accessibility)
- Out of scope (explicit exclusions)
User Flows
- Primary happy path
- Key decision points
- Error states and recovery
Technical Considerations
- Architecture implications
- Integration points
- Data requirements
- Migration needs
Timeline and Milestones
- Phase breakdown with deliverables
- Dependencies and risks
Open Questions
- Decisions that need stakeholder input
- Areas requiring further research
Output
- Complete PRD in markdown format
- Ready for stakeholder review

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.

5d ago First seen · 68 lines · 5 tokens per session scan A 90f08fe6bfac

Subscribe to this mod's changes

prd is a command published in the GitHub repository CrashBytes/claude-role-skills (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 382 once invoked, about $0.0000 per session on Opus 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-08-31.

Planning Writing and docs agent-skills claude-code claude-plugin claude-skills infosec

prd

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Product Requirements Document

Arguments

Workflow

What this file has done since we first saw it

Other commands, from other repositories

save

launch-meta-campaign

negative-keyword-sweep

import

index

check