Menú
Start implementation with a red test. Use on any bugfix or new behavior — not on refactors or style changes.
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
Pick the right worker class for each Issue. Use every time you assign an Issue; wrong routing wastes tokens and creates rework.
Break a Company Goal into 3-10 atomic Issues. Use when a Goal arrives with no pre-existing plan and you need to produce a shippable work list.
Ship the smallest change that solves the Issue. Use on every implementation task; scope creep is the default failure mode of executors.
Run build/test/lint and read the actual output before claiming done. Use on every implementation task, at the end.
Report research results in a form other agents can act on. Use at the end of every Explorer session.
Find files and code patterns fast. Use for every codebase question that starts with "where is X" or "how is Y used".
| name | write-failing-test-first |
| description | Start implementation with a red test. Use on any bugfix or new behavior — not on refactors or style changes. |
Writing the test before the code is not a performance — it's a forcing function for two things: (a) proving the symptom before you chase a fix, (b) giving yourself a concrete "done" signal you cannot fake.
