Menú
Capture an architectural decision so the next session (or engineer) knows WHY. Use after any non-obvious technical choice.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Calibrate a reviewer persona with few-shot rubric examples so skepticism stays consistent and doesn't drift lenient over long runs.
Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order. The ledger fresh-context sessions read to know what's done, what's next, and what they're forbidden to touch.
Systematically remove one harness component at a time and measure impact, killing scaffolding that no longer earns its complexity.
Author idempotent init.sh under 120s plus sibling test.sh, stop.sh, reset.sh, serve.sh with fixed names the harness relies on.
Expand a 1-4 sentence product brief into a full spec with a design language, acceptance surface, and an ordered feature list.
Run the fixed 6-step session-opening sequence — pwd, read progress, git log, count remaining features, init.sh, smoke-test last feature — before touching any new work. The orientation ritual that lets fresh-context sessions reconstruct project state in under a minute.
| name | decision-record |
| description | Capture an architectural decision so the next session (or engineer) knows WHY. Use after any non-obvious technical choice. |
| when_to_use | picked a library/pattern/schema, a tradeoff was made, a hard-to-reverse choice |
Write a short file docs/decisions/NNN-<slug>.md:
