tdd

The red-green-refactor cycle in test-driven development involves writing a failing test first, implementing minimal code to make it pass, and then refactoring both test and production code for high quality and maintainability.

To start test-driven development for a new feature, activate the tdd process to automatically detect your project's testing stack, write a failing test, and then write the minimal code required to make that test pass.

Yes, the tdd workflow automatically detects your project-specific testing stack, including the programming language, test framework, conventions, and tooling, ensuring the test-driven development cycle integrates seamlessly with your existing setup.

Test-driven development integrates with code refactoring by connecting to code quality skills for naming and function decomposition, allowing you to clean up and refactor both test and production code after achieving a passing test state.

Use test-driven development when starting a new feature to ensure robust, well-tested code by writing tests before implementation, guiding you to write minimal code and refactor afterward for better code quality and maintainability.

The test-driven development cycle focuses on guiding the red-green-refactor process and detecting project testing stacks, but requires integration with separate code quality skills for advanced naming and function decomposition during complex refactoring tasks.