ProductFlow: Command for Claude Code

.claude/commands/discovery.md

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

A user-research assistant for studying interviews, surveys, and other qualitative feedback. It can also prepare interviews and map user needs to possible solutions.

In plain words
What is it for?
Analyzing research, creating interview guides, building an Opportunity Solution Tree, mapping Jobs-to-be-Done, and synthesizing findings.
Why use it?
It turns scattered user feedback into patterns, user jobs, opportunities, and experiments that can guide product decisions.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/matheusbrramos/productflow/discovery"><img src="https://agentmods.dev/badge/commands/matheusbrramos/productflow/discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 657 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.00011 $0.00657
Opus 5.5 $0.00004 $0.00263
Sonnet 5.5 $0.00002 $0.00131
Haiku 4.5 $0.00001 $0.00066

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

Security

Grade A, and why

discovery 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/discovery.md · 106 lines

How it starts

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

/discovery - Analise de Usuarios

Realiza pesquisa qualitativa de usuarios usando o agente Discovery.

Entrada

$ARGUMENTS

Se nenhum argumento for fornecido, perguntar:

  • Qual acao deseja? (analyze, interview, ost, jtbd, synthesize)
  • Quais dados ou contexto fornecer?

Pre-requisitos

Verificar se .context/empresa.md existe. Se nao existir, orientar a rodar /setup primeiro.

Acoes Disponiveis

analyze

Analisa transcricoes de entrevistas, surveys ou dados qualitativos.

O que fazer:

  1. Processar dados fornecidos
  2. Extrair quotes relevantes
  3. Identificar padroes (critico, importante, relevante)
  4. Mapear Jobs-to-be-Done
  5. Sugerir oportunidades

interview

Prepara guia de entrevista para um perfil especifico.

O que fazer:

  1. Definir objetivo da entrevista
  2. Criar estrutura (abertura, contexto, experiencia, momento critico)
  3. Incluir dicas de conducao
  4. Gerar perguntas no formato correto (comportamento, nao hipotetico)

ost

Cria ou atualiza Opportunity Solution Tree.

O que fazer:

  1. Definir outcome de negocio
  2. Mapear oportunidades dos usuarios
  3. Listar solucoes por oportunidade
  4. Sugerir experimentos de validacao

jtbd

Mapeia Jobs-to-be-Done de um segmento.

O que fazer:

  1. Identificar job principal
  2. Mapear jobs secundarios
  3. Usar formato: QUANDO [situacao] QUERO [motivacao] PARA QUE [resultado]

synthesize

Consolida todos os insights de discovery em um documento.

Output

Criar arquivo com formato: docs/discovery/{tema}-YYYY-MM-DD.md

Estrutura do Output

# Analise de Discovery - [Tema]

**Data:** YYYY-MM-DD
**Entrevistas:** N
**Perfil:** [descricao]

## Jobs-to-be-Done
### Job Principal
### Jobs Relacionados

## Padroes Identificados
### Critico (N/N mencionaram)
### Importante (N/N mencionaram)
### Relevante (N/N mencionaram)

## Oportunidades
## Recomendacoes
## Anexo: Quotes

Proximos passos sugeridos

  • /prd <feature> - Criar especificacao
  • /research - Complementar com pesquisa de mercado

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

  1. 2mo ago First seen · 106 lines · 11 tokens per session scan A 944fbe148fb3

Subscribe to this mod's changes

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

discovery compared with commands from other repositories

discovery next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
discoverymatheusbrramos/ProductFlowCommand27mo agoMITA11Claude 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