run-tdd

To run a red-green-refactor TDD cycle, you start by creating implementation stubs and writing failing unit tests for Stage F RED, implement minimal code to pass tests for Stage G GREEN, and finish by refactoring with integration tests for Stage H REFACTOR.

The docs-first TDD workflow is a structured testing lifecycle that ensures teams start with failing tests, implement minimal functional code, and perform quality validation. You need it to streamline end-to-end test-driven development across RED, GREEN, and REFACTOR stages.

To handle contract changes during the GREEN phase of TDD, you follow the Stage G.1 protocol after implementing minimal functional code to pass tests. This protocol identifies and manages contract changes to maintain integration readiness across the workflow.

To perform quality validation during code refactoring, you add integration tests and refactor the code while keeping tests green, then complete the structured quality validation process defined in Stage H.4 to ensure software integrity.

Yes, you can enforce test categorization and integration readiness by coordinating a structured TDD workflow across stages. This approach enforces specific test categorization protocols and provides guidance on stubs and validation scripts to ensure readiness.

The best way to start a TDD cycle is to initiate the process to guide you through Stage F RED, where you create implementation stubs and write failing unit tests to validate the red phase before moving to minimal code implementation.