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.
npx agentmods add commands/doncheli/don-cheli-sdd/prdgit clone --depth 1 https://github.com/doncheli/don-cheli-sddWrote 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/doncheli/don-cheli-sdd/prd)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/prd"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/prd.svg" alt="Measured on agentmods" 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 | $0.00099 | $0.01386 |
| Opus 5 | $0.00049 | $0.00693 |
| Sonnet 5 | $0.00020 | $0.00277 |
| Haiku 4.5 | $0.00010 | $0.00139 |
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 yesterday.
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:prd — Generador de PRD
Objetivo
Generar un Product Requirement Document profesional desde múltiples fuentes de input, listo para alimentar el pipeline SDD.
Uso
/dc:prd # Modo interactivo — pregunta fuentes
/dc:prd "Descripción del producto" # Desde descripción en lenguaje natural
/dc:prd --figma <link> # Desde diseño en Figma
/dc:prd --brief docs/brief.md # Desde brief de producto
/dc:prd --figma <link> --brief brief.md # Múltiples fuentes combinadas
/dc:prd --template saas # Usar template específico (saas, mobile, ecommerce, api, internal, landing)
/dc:prd --version 1.1 # Crear nueva versión de PRD existente
Comportamiento
Lee la habilidad habilidades/generador-prd/HABILIDAD.md para el proceso completo.
Proceso resumido:
1. DESCUBRIR — Leer todas las fuentes (Figma, docs, conversación, codebase)
2. ESTRUCTURAR — Organizar en 13 secciones con priorización MoSCoW + RICE
3. ANALIZAR — Riesgos (7 categorías), dependencias, estimación de esfuerzo
4. REDACTAR — PRD completo con user stories Gherkin, diagramas Mermaid, timeline
5. VALIDAR — ¿Requirements verificables? ¿Métricas definidas? ¿Scope claro?
6. ENTREGAR — Markdown + Gherkin + diagrama + matriz de riesgos
Análisis de Figma
Cuando se proporciona un link de Figma:
- Reconocer — Identificar pantallas, flujos, componentes
- Extraer — Textos, formularios, interacciones, estados
- Analizar gaps — Estados faltantes (loading, error, empty, offline)
- Convertir — Cada pantalla → user stories → criterios de aceptación
Análisis de riesgos
Para cada feature evalúa automáticamente:
| Categoría | Qué evalúa |
|---|---|
| Técnico | Complejidad, integraciones, deuda técnica |
| Producto | Market fit, adopción, competencia |
| UX | Usabilidad, accesibilidad, learning curve |
| Negocio | Revenue, costo, time-to-market |
| Legal | GDPR, compliance, términos |
| Seguridad | OWASP, datos sensibles, auth |
| Operacional | Soporte, escalabilidad, monitoring |
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.
- yesterday First seen · 149 lines · 99 tokens per session scan A 4a1024656569
prd is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 25d ago), licensed Apache-2.0. It adds 99 tokens to every session and 1,386 once invoked, about $0.0005 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-09-03.
Other commands, from other repositories
add-phase
Add phase to end of current milestone in roadmap.
insert-phase
Insert urgent work as decimal phase (e.g., 72.1) between existing phases.
reapply-patches
Reapply local modifications after a PBR update.
remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
research-phase
Research how to implement a phase (standalone — usually use /pbr:plan-phase instead).
update
Update PBR to latest version with changelog display.