tdd-workflow

Test-driven development orchestrates writing failing tests first (RED), implementing minimal code to pass them (GREEN), improving code quality (REFACTOR), and committing with requirement traceability (COMMIT). This Skill automates that full cycle, enforcing discipline across all four phases while maintaining REQ-* lineage from requirement to code.

Yes. The TDD workflow integrates pytest for test generation and execution, and requires a git repository for traceable commits linked to REQ-* identifiers. It automates quality gates to ensure tests pass and technical debt is addressed before committing.

You need a git repository initialized, pytest installed, and a requirement identifier (REQ-*) that describes the feature to implement. The workflow validates these prerequisites before guiding you through test writing, code implementation, refactoring, and the final commit.

Requirement traceability embeds REQ-* tags throughout the TDD workflow—from test generation through refactoring to the final commit. This creates complete lineage documentation showing how each code change connects back to the original requirement.

Manual testing lacks enforced discipline and traceability. TDD workflow coordinates the complete RED-GREEN-REFACTOR-COMMIT sequence, enforces quality gates automatically, ensures tests drive design, and generates traceable commits—eliminating gaps and inconsistency in the development cycle.

Use TDD workflow when implementing features that require audit trails, maintaining code quality standards, or working in environments demanding requirement traceability. It's essential for regulated development, team consistency, and preventing technical debt accumulation during feature implementation.