test-driven-development

Test-driven development is a test-first practice that eliminates undetected bugs by requiring a mandatory failing test before writing minimal implementation code. This approach prevents costly post-deployment debugging and ensures reliable software behavior across any codebase.

To apply the Red-Green-Refactor cycle, first write a failing test for the new feature behavior, then create the minimal implementation required to pass the test, and finally refactor the code while maintaining test guardrails to verify reliable production output.

Yes, test-first practices apply to all bug fixes, refactoring, and behavior changes. You must write a failing test verifying the specific bug or expected behavior change before writing any implementation code, ensuring the fix works as expected from the start.

The best way to avoid testing anti-patterns is by following strict step-by-step Red-Green-Refactor rules with built-in countermeasures for common workflow rationalizations, enforcing mandatory failing test verification and minimal implementation guardrails.

You should not bypass test-driven development for any feature implementation, bug fix, refactoring, or behavior change task. The Skill enforces mandatory test-first software development practices across all codebase modifications to eliminate hidden bugs.