Menu
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR.
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
Automated governance, hook installation, pre-commit validation, branch isolation, and safe commit operations.
Enforcement of safety guardrails, axiom verification, secret scanning, and mutability protections.
Building and managing premium statistical dashboards, RAG explorer UIs, warehouse log monitors, and real-time visualization centers.
Integration of agent systems with blockchain protocols, contracts, event stores, reputation networks, and collective verification engines.
AI model configuration, LLM memoization, agentic RAG search, and vector library maintenance.
Catalog generation, reference link verification, workshop documentation building, and knowledge gap analysis.
| name | test-driven-development |
| description | Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR. |
| type | skill |
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
No exceptions without User permission.
Write one minimal test showing what should happen.
MANDATORY. Never skip. Confirm: Test fails (not errors) because feature is missing.
Write simplest code to pass the test. Do not over-engineer (YAGNI). Don't add features, refactor other code, or "improve" beyond the test.
MANDATORY. Confirm: Test passes and all other tests still pass.
After green only: Remove duplication, improve names, extract helpers. Keep tests green. Don't add behavior.
| Excuse | Reality |
|---|---|
| "Too simple to test" | Simple code breaks. Test takes 30 seconds. |
| "I'll test after" | Tests passing immediately prove nothing. |
| "Tests after achieve same goals" | Tests-after = "what does this do?" Tests-first = "what should this do?" |
| "Already manually tested" | Ad-hoc โ systematic. No record, can't re-run. |
Before marking work complete, ensure:
If you are stuck, write a wished-for API or ask the User for help.