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/planninggit 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/planning)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/planning"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/planning.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.1 | $0.00024 | $0.03055 |
| Opus 5 | $0.00012 | $0.01528 |
| Sonnet 5 | $0.00005 | $0.00611 |
| Haiku 4.5 | $0.00002 | $0.00305 |
Grade A, and why
planning 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 2d 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dc:planning
Objetivo
Facilitar el planning semanal de un equipo de desarrollo: revisar RFCs pendientes, priorizar trabajo, asignar tareas a responsables individuales, parejas o squads, y generar un plan accionable con compromisos claros.
A diferencia de /dc:estimar (esfuerzo por tarea) o /dc:debate (decisiones técnicas), el planning opera a nivel de equipo y sprint: qué se hace, quién lo hace, en qué orden, y qué se deja fuera.
Uso
/dc:planning # Planning completo (interactivo)
/dc:planning --semana "2026-03-24" # Planning para semana específica
/dc:planning --equipo "Ana,Carlos,Luis,María" # Definir equipo
/dc:planning --capacidad "Ana:4d,Carlos:3d" # Capacidad por persona (días disponibles)
/dc:planning --rfcs "RFC-012,RFC-015,RFC-018" # RFCs a revisar
/dc:planning --modo revision # Solo revisión de RFCs (sin asignación)
/dc:planning --modo asignacion # Solo asignación (RFCs ya priorizados)
/dc:planning --modo seguimiento # Revisar avance del planning anterior
Proceso (4 Fases)
Fase 1: Contexto del equipo
Recopilar información del equipo antes de planificar:
## Contexto del equipo
### Miembros y disponibilidad
| Miembro | Rol | Disponibilidad | Notas |
|---------|-----|----------------|-------|
| Ana | Sr. Backend | 4/5 días | Lunes feriado |
| Carlos | Sr. Frontend | 5/5 días | — |
| Luis | Fullstack | 3/5 días | 2 días en soporte rotativo |
| María | Sr. Backend | 5/5 días | — |
| Diego | Jr. Frontend | 5/5 días | Necesita mentoring |
### Capacidad total del equipo
- Días disponibles: 22/25 (88%)
- Factor de foco (reuniones, interrupciones): 0.7
- **Capacidad efectiva: 15.4 días-persona**
### Arrastre de la semana anterior
- [ ] RFC-010: Migración de auth — 60% completado (María, bloqueo en revisión de seguridad)
- [x] RFC-011: Endpoint de reportes — completado
- [ ] BUG-234: Memory leak en worker — pendiente (Luis no tuvo disponibilidad)
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.
- 2d ago First seen · 265 lines · 24 tokens per session scan A ed4ce52d872c
planning is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 25d ago), licensed Apache-2.0. It adds 24 tokens to every session and 3,055 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-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.
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).
reapply-patches
Reapply local modifications after a PBR update.
update
Update PBR to latest version with changelog display.