tdd-red-green-refactor

The Red-Green-Refactor cycle structures TDD into three phases: write a failing test (Red), write minimal code to pass it (Green), then improve code quality (Refactor). This Skill provides patterns, checklists, and decision criteria to enforce each phase consistently across F# domain and C# application layers, including unit-test orchestration and coverage targets of 80% overall and 100% for Domain code.

Test coverage management in TDD requires setting realistic targets and monitoring them systematically. This Skill guides coverage setup, establishes targets (80% overall, 100% Domain), and integrates with the unit-test agent to validate architectural conformance and naming conventions, ensuring coverage becomes part of your development workflow rather than an afterthought.

Yes. The Red-Green-Refactor patterns apply across new feature implementation, bug fixes, and refactoring. This Skill provides use-case-specific checklists and decision criteria for each scenario, helping you maintain consistent TDD practices regardless of whether you're adding functionality or improving existing code.

This Skill includes practical patterns for unit-test agent orchestration and dependency injection guidance tailored to F# and C# stacks. It provides setup instructions and best-practice checklists that help you configure testable code structures aligned with architectural conformance requirements and naming conventions.

TDD effectiveness depends on consistent naming conventions and architectural alignment. This Skill provides checklists for test naming, integrates with ADR_009 and related guiding skills, and includes decision criteria for architectural conformance, ensuring your tests and code organization reinforce each other.