test-driven-development

To enforce test-driven development for every code change, the Skill requires explicit tests before implementation and ensures red-green-refactor cycles. It gates progression through THINK and PLAN stages across new features, bug fixes, and refactors.

The red-green-refactor cycle is a test-driven development process where a failing test is written first, minimum code is implemented to pass it, and then the code is refactored. The Skill automatically enforces this cycle and deletes untested code.

Automate quality assurance for new features and bug fixes by applying strict test-driven development discipline. The Skill gates code progression through THINK and PLAN stages, requiring failing tests before implementation to ensure correct, reliable code.

Yes, test-driven development works for refactoring existing software projects. The Skill applies red-green-refactor cycles across software projects, enforcing the deletion of untested code and requiring explicit tests before implementing any refactored changes.

To start writing a failing test before implementing code, describe a feature or bug, then let the Skill write the failing test. It will implement the minimum code required to pass the test, enforcing the red-green-refactor cycle.

Test-driven development requires deleting untested code to enforce strict quality assurance and reliability. By applying the Delete Untested Code rule, the Skill ensures only verified, tested implementations progress through the red-green-refactor cycle.