test-driven-development

The red-green-refactor cycle in test-driven development requires writing a failing test first, implementing minimal production code to pass it, and then refactoring while keeping tests green to ensure correct software behavior and safer code improvements.

To start writing tests before production code, write a failing test that captures the desired behavior, implement the minimal code to pass the test, run tests to confirm failure then success, and refactor for readability while preserving behavior.

You need test-driven development during refactoring and bug fixes to ensure clear expectations and regression coverage, reducing the risk of breaking existing functionality while improving code maintainability and software correctness.

Test-driven development as implemented here requires no specific testing frameworks or external dependencies, mandating only a YAML frontmatter with name and description in SKILL.md, and may optionally include scripts and references for deterministic testing.

Test-driven development reduces regressions in software engineering by enforcing tests before production code, ensuring that every feature and bug fix has clear expectations and regression coverage that prevents future behavior breaks.

The best way to maintain code quality during feature development is using test-driven development, which enforces a failing test before implementation, guiding minimal code changes and enabling safe refactoring while keeping tests green.