Menú
Write implementation plans as test-addressed red-green-refactor cycles rather than component waterfalls.
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
Fine-grained outside-in RED-GREEN-REFACTOR microcycles with specialist agents and single-diagnostic implementation.
RGR sequence, observed-failure evidence, drill-down unit tests, and non-behavioral exemptions for Phoenix/Commanded work.
Phoenix 1.8, Postgres, Commanded, Ecto, ExUnit, Dialyzer, and strict static-check conventions.
Phoenix auth/session/CSRF, command authorization, event data sensitivity, Postgres, dependency, secret, and threat-model review triggers.
Process Forgejo PR feedback with reflection, guardrail-gap classification, and inline thread replies.
Classify review feedback and choose proportionate guardrails without inflating default context cost.
| name | rgr-plan-structure |
| description | Write implementation plans as test-addressed red-green-refactor cycles rather than component waterfalls. |
Use this skill before writing plans, todo lists, PR checklists, or session outlines for behavior work.
RGR-shaped plans name the failing test that justifies each production edit. They keep at most one active cycle in progress and avoid speculative downstream component tasks.
Waterfall plans list components in construction order: models, events, handlers, persistence, UI, then tests. If a task cannot name the failing test it addresses, it is speculative.
Cycle 1:
<test name> for <observable behavior> and run <command>.<command> is green.Repeat only after the previous cycle is green.