developer-feature

To implement features using Test-Driven Development, this Skill automates the strict Red-Green-Refactor cycle. It mandates writing failing unit and integration tests before writing minimal production code, then refactoring for quality and API documentation.

The TDD process for automated feature development follows the Red-Green-Refactor cycle. This Skill enforces creating failing tests first, writing minimal code to pass them, and finally refactoring to ensure robust, production-ready code from the outset.

To start writing unit and integration tests before implementation, define the feature requirements like a user authentication module. This Skill guides you through creating tests for login, logout, and error handling before developing the actual logic.

Yes, you can automate test creation for a new authentication module. This Skill enforces automated testing from the initial phase, ensuring tests for login, logout, and error handling are written and passing before implementation.

Test-driven feature implementation includes API documentation as a final deliverable. Following the Red-Green-Refactor cycle, this Skill ensures code is refactored for quality and that comprehensive API documentation is generated.

You should use a strict TDD cycle for software engineering when adding new features that require production-ready robustness. It ensures automated testing is prioritized from the initial phase, preventing regressions and enforcing quality.