test-driven-development

Test-driven development improves code quality by requiring you to write a failing test first, then writing minimal code to pass it. This enforces the Red-Green-Refactor cycle, ensuring every feature has automated verification before implementation.

The Red-Green-Refactor cycle is a test-driven development practice where you write a failing test (Red), implement minimal code to make it pass (Green), and then clean up the code without changing its behavior (Refactor). This enforces quality through continuous testing.

To implement a feature using TDD, activate the skill and execute the delegate_task command. This guides you through writing a failing test first, creating minimal code to pass the test, and then refactoring the implementation to enforce quality.

Yes, you can use test-driven development across all stages of software development. It enforces quality through testing and refactoring at every step, ensuring your features are backed by automated verification regardless of the project phase.

Yes, test-driven development provides scripts for automating test runs to verify that each test case works as expected. This automated verification ensures your minimal code passes the failing tests before you proceed to the refactoring stage.

Writing a failing test before coding enforces the test-driven development cycle by validating that the test itself is functional. It ensures you only write minimal code necessary to pass the test, directly improving overall code quality and preventing over-engineering.