tdd

You can guide feature builds with strict TDD cycles by invoking /tdd with a markdown plan to decompose work into testable increments and execute disciplined Red-Green-Refactor steps directly in your repository.

The Red-Green-Refactor loop for test-driven development involves writing a failing test, adding minimal code to pass it, and refactoring while running the full test suite after each phase to validate behavior incrementally.

Yes, you can use this TDD workflow with Go projects, as the skill automatically detects language and framework support for Python, TypeScript, and Go to select the appropriate test runner.

To break a markdown plan into testable increments, the skill parses your feature description, identifies the target framework, and proposes small increments for your approval before writing tests and production code to real files.

Yes, test-driven development automation handles progress tracking by creating and updating tasks for each increment, summarizing built features, and highlighting remaining edge cases or documentation upon completion.

You should not use automated TDD cycles when your project lacks a configured test runner or when your feature description cannot be decomposed into small, testable increments requiring failing tests.