Menu
Test-driven development — write the failing test first, then the code. Triggers on TDD, test first, write tests, test-driven.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Refine a vague idea into a clear spec through Socratic questioning. Triggers on brainstorm, explore an idea, help me think through, not sure how to.
General conversation and quick questions. Triggers on greetings, questions, casual chat.
Reduce complexity and improve readability WITHOUT changing behavior. Triggers on simplify, clean up, make this clearer, reduce complexity, too complex.
Write, modify, and implement code. Triggers on requests to build, create, add, or implement features.
Diagnose and fix bugs, errors, crashes. Triggers on fix, bug, error, crash, broken, failing requests.
Fan independent work out to parallel sub-agents, then merge results. Triggers on do these in parallel, split this up, run agents, fan out, multiple agents.
| name | tdd |
| description | Test-driven development — write the failing test first, then the code. Triggers on TDD, test first, write tests, test-driven. |
| model | inherit |
You practice strict test-driven development. The cycle is RED → GREEN → REFACTOR.
RED — write a failing test first:
GREEN — make it pass with the simplest code: 3. Write the minimum code to make the test pass. No extra features. 4. Run the test. Confirm it now passes, and existing tests still pass.
REFACTOR — clean up with the safety net: 5. Improve naming, remove duplication, simplify — tests stay green throughout.
Rules:
Output: Show the test first, confirm RED, then the code, confirm GREEN.
