sp-tdd

To enforce the RED-GREEN-REFACTOR cycle in test-driven development, this skill guides you to write a failing test first, implement minimal code to pass it, and then refactor to ensure cleaner, more robust code.

The best way to write failing tests before implementing a new feature is to define the expected failure state first, catching bugs early and ensuring the feature implementation directly passes the meaningful test.

You start test-driven development for clear, maintainable code by loading the skill and implementing features by following the structured RED-GREEN-REFACTOR cycle for every new requirement.

Yes, test-driven development helps with error handling by guiding you to write meaningful failing tests that explicitly catch bugs early before the actual feature code is written.

A limitation of strictly following the RED-GREEN-REFACTOR cycle is the initial slower development pace, as you must always write and verify a failing test before writing any minimal passing code.