Um comando para transformar um PRD — documento que descreve uma funcionalidade ou produto — em histórias de usuário detalhadas. Cada história explica quem precisa de algo, o que quer fazer e por quê, com critérios de aceitação em formato Given/When/Then.

Serve para identificar requisitos, personas e épicos; escrever histórias independentes; manter rastreabilidade; e definir critérios de aceitação para desenvolvimento e testes.

Ajuda a dividir requisitos grandes em tarefas verificáveis e a cobrir o caminho principal, exceções e casos extremos. Exige um PRD aprovado e pede a escolha do modelo antes de escrever.

How matheusbrramos/ProductFlow configures Claude Code

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/stories.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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/matheusbrramos/productflow/stories/github.svg)](https://agentmods.dev/commands/matheusbrramos/productflow/stories)

Your own site

<a href="https://agentmods.dev/commands/matheusbrramos/productflow/stories"><img src="https://agentmods.dev/badge/commands/matheusbrramos/productflow/stories/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/matheusbrramos/productflow/stories"><img src="https://agentmods.dev/badge/commands/matheusbrramos/productflow/stories.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 624 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.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.00624
Opus 5.5	$0.00004	$0.00250
Sonnet 5.5	$0.00002	$0.00125
Haiku 4.5	$0.00001	$0.00062

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

Security

Grade A, and why

stories 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/stories.md · 112 lines

How it starts

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

/stories - Criar User Stories Detalhadas

Cria user stories detalhadas usando o agente Story-Writer.

Entrada

$ARGUMENTS

Se nenhum argumento for fornecido, perguntar qual feature ou PRD detalhar.

Pre-requisitos

PRD aprovado (criado por /prd)
.context/empresa.md deve existir

Se PRD nao existir, orientar a rodar /prd primeiro.

Selecao de Modelo

SEMPRE perguntar ao PM antes de comecar:

Qual modelo voce deseja usar para esta sessao de escrita de stories?

1. **Modelo completo** (Sonnet/Opus) - Para stories complexas com muitos edge cases
2. **Modelo economico** (Haiku) - Para stories simples e bem definidas
3. **Deixar eu decidir** - Vou sugerir baseado na complexidade da tarefa

Aguardo sua escolha antes de prosseguir.

O que fazer

Analisar PRD ou feature
- Identificar requisitos funcionais
- Entender personas e JTBD
- Mapear epicos
Quebrar em user stories
- Formato: Como [persona] Quero [acao] Para [beneficio]
- Garantir independencia (INVEST)
- Manter rastreabilidade aos requisitos
Escrever acceptance criteria
- Formato Gherkin (Given/When/Then)
- Cobrir cenario principal (happy path)
- Cobrir excecoes e edge cases
Adicionar metadata
- Prioridade (P0/P1/P2/P3)
- Estimativa (XS/S/M/L/XL)
- Dependencias entre stories
- Definition of Done

Output

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

Estrutura do Output

# User Stories - [Feature]

**PRD:** [referencia]
**Data:** YYYY-MM-DD
**Modelo usado:** [completo/economico]

## Story Map
[Visualizacao opcional]

## Stories

### US-001: [Titulo]
**Epic:** [nome]
**Requisitos:** [RF-XXX]

**Como** [persona]
**Quero** [acao]
**Para** [beneficio]

#### Acceptance Criteria
```gherkin
Scenario: [descricao]
  Given [contexto]
  When [acao]
  Then [resultado]

Prioridade: P0 Estimativa: M Dependencias: -


## Proximos passos sugeridos

- `/pf-review` - Revisar qualidade das stories
- Entregar para time de desenvolvimento

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

2mo ago First seen · 112 lines · 9 tokens per session scan A eebc97da1765

Subscribe to this mod's changes

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

Planning Writing and docs

stories next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
storiesmatheusbrramos/ProductFlow	Command	2	7mo ago	MIT	A	9	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

ProductFlow: Command for Claude Code