Menu
Use before changing behavior or fixing a bug when a focused test can prove the change.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when waiting for servers, jobs, files, tests, queues, or external processes.
Use when a bounded subtask is summarization, mechanical review, fixture inspection, proposal triage, verification, or boilerplate.
Use when locating where a symbol, function, type, command, or constant is defined or referenced, instead of grep/find/read chains.
Use when tempted to add broad abstractions, future-proofing, or extra product surface beyond the requested change.
Use before asking the user about infrastructure, preferences, conventions, prior decisions, or past incidents.
Use when evaluating reviewer feedback, review delegates, or suggested code changes.
| name | test-driven-development |
| description | Use before changing behavior or fixing a bug when a focused test can prove the change. |
| source | bundled |
| triggers | {"tool":["Write","Edit","MultiEdit"],"path_pattern":["_test.","test_"]} |
Use this when behavior is changing and the system can express the desired result as a test.
Work in this order:
Do not treat a compile error, unrelated fixture failure, or unrun test as a valid red phase. The red phase must show the behavior gap you intend to close.
