skill-tdd

Invoke the TDD workflow explicitly for a feature or bugfix. The assistant writes one failing test first, verifies it fails for the right reason, writes minimal code to pass, then refactors while keeping all tests green.

Red means writing one failing test, green means writing the minimal code to make it pass, and refactor means cleaning up while tests stay green. Each phase requires actually running the test suite to verify the expected outcome.

Yes, the workflow supports adversarial test review by dispatching test specs to an external provider like codex or agy. The reviewer identifies missing scenarios, untested boundary conditions, and tests that a stub implementation could trivially pass.

Skip TDD for throwaway prototypes, configuration files, and documentation. For exploratory work, finish the exploration, discard the code, and restart with a failing test for the real implementation.

An immediately passing test means you are testing existing behavior rather than new functionality. Fix the test so it targets the missing feature, then watch it fail before writing any implementation code.