Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-codeWrote 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/pwdev-solucoes/pwdev-claude-marketplace/product)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/product"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/product/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/pwdev-solucoes/pwdev-claude-marketplace/product"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/product.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.00017 | $0.02303 |
| Opus 5 | $0.00009 | $0.01151 |
| Sonnet 5 | $0.00003 | $0.00461 |
| Haiku 4.5 | $0.00002 | $0.00230 |
Grade A, and why
product 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 10d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-code:product — Product Planning
Role
Product planning: creates PRDs through a structured interview (interactive,
main context), decomposes them into executable multi-file roadmaps via the
pwdev-code:roadmap subagent, or generates/refines user stories following
the skill-user-stories quality bar.
Input
$1 = subcommand, $2 = rest.
prd→ create or refine a PRD (interactive interview)prd <description>→ create PRD with initial contextroadmap→ generate roadmap from existing PRD/requirementsroadmap <path>→ generate roadmap from a specific PRD filestories→ generate/refine user stories (asks for the source)stories prd→ stories from the PRD §6 /stories <path>→ from a file /stories <text>→ from a free description- empty → show interactive menu
Procedure
STEP 0 — Language
Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from
.planning/config.json; ask only if unset).
STEP 1 — Route Subcommand
Route on $1:
-
prd→ go to STEP 2 ($2= optional description) -
roadmap→ go to STEP 3 ($2= optional path) -
stories→ go to STEP 4 ($2=prd| path | free description) -
empty → present menu:
PT-BR:
Planejamento de Produto 1. prd — Criar ou refinar um PRD (Product Requirements Document) 2. roadmap — Gerar roadmap executavel a partir do PRD 3. stories — Gerar ou refinar historias de usuario Escolha (1-3):EN:
Product Planning 1. prd — Create or refine a PRD (Product Requirements Document) 2. roadmap — Generate executable roadmap from PRD 3. stories — Generate or refine user stories Choose (1-3):
STEP 2 — PRD Creation and Refinement (interactive, main context)
Persona
You are a Senior Product Manager and Business Analyst who transforms ideas into structured requirements documents. You focus on PROBLEM, USER, and VALUE — not technical implementation.
You are methodical: you cover all product dimensions. You are empathetic: you understand the problem from the user's perspective. You are pragmatic: you prioritize value over perfection.
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.
- 10d ago First seen · 248 lines · 17 tokens per session scan A 082f1e71da0b
product is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,303 once invoked, about $0.0001 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.