ProductFlow: Command for Claude Code

.claude/commands/prd.md

prd is a command for Claude Code from matheusbrramos/ProductFlow. It costs 6 tokens per session (500 once invoked), scanned A, original, MIT.

A command for creating a Product Requirements Document, a written plan describing what a product or feature should do and why. It uses company context, discovery findings, and market research when available.

In plain words
What is it for?
Producing requirements, user context, functional and non-functional needs, scope, risks, success metrics, and high-level work items for a feature or product.
Why use it?
It helps turn scattered evidence and assumptions into traceable requirements, while marking unanswered questions.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

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

Reuse

Borrowing it

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

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 prd

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/matheusbrramos/productflow/prd"><img src="https://agentmods.dev/badge/commands/matheusbrramos/productflow/prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 500 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.00006 $0.00500
Opus 5.5 $0.00002 $0.00200
Sonnet 5.5 $0.00001 $0.00100
Haiku 4.5 $0.00001 $0.00050

Measured 2mo ago against content hash 5fc40792db38, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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/prd.md · 76 lines

What it actually says

/prd - Criar Product Requirements Document

Cria PRD completo usando o agente Strategist.

Entrada

$ARGUMENTS

Se nenhum argumento for fornecido, perguntar o nome da feature ou produto.

Pre-requisitos

  1. Verificar se .context/empresa.md existe
  2. Recomendado: Discovery e pesquisa de mercado concluidos

Se pre-requisitos nao atendidos, orientar quais comandos rodar primeiro.

O que fazer

  1. Entender o problema

    • Analisar evidencias de discovery
    • Verificar analise competitiva
    • Questionar premissas
  2. Criar PRD completo com todas as secoes:

    • Sumario Executivo (problema, evidencias, solucao, outcome)
    • Contexto (JTBD, personas, jornada)
    • Requisitos Funcionais (detalhados, categorizados, priorizados)
    • Requisitos Nao-Funcionais (performance, seguranca, compliance, etc)
    • Escopo (in/out, premissas, restricoes)
    • Epicos (alto nivel)
    • Metricas de Sucesso
    • Riscos
  3. Marcar ambiguidades

    • Usar [NEEDS CLARIFICATION] para questoes pendentes
    • Listar premissas a validar
  4. Garantir rastreabilidade

    • Cada requisito linkado a evidencia
    • Referencias a docs de discovery e research

REGRAS CRITICAS

  • Definir O QUE e POR QUE, nunca o COMO
  • Nao escrever codigo ou fazer decisoes tecnicas
  • Nao incluir features especulativas
  • Todos os requisitos devem ser testaveis

Output

Criar arquivo: docs/prd/{feature}.md

Usar estrutura completa do PRD com todas as secoes obrigatorias.

Proximos passos sugeridos

  • /pf-review - Revisar qualidade do PRD
  • /stories <feature> - Detalhar user stories
  • /pf-spec <feature> - Criar Software Design Document

Exemplos

/prd "Alertas inteligentes de vendas"
/prd "Sistema de autenticacao"
/prd "Modulo de relatorios"
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 · 76 lines · 6 tokens per session scan A 5fc40792db38

Subscribe to this mod's changes

prd is a command published in the GitHub repository matheusbrramos/ProductFlow (2 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 500 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-08-31.

Related

prd compared with commands from other repositories

prd next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
prdmatheusbrramos/ProductFlowCommand27mo agoMITA6Claude 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