tdd-pipeline

Automating an end-to-end TDD workflow involves orchestrating spec validation, behavior catalog enumeration, test generation, and aligned code implementation. This pipeline automates those steps sequentially, applying a human-in-the-loop gate to validate behavior contracts before proceeding to code generation and commit.

Durable behavior catalogs for TDD are maintained by enumerating behaviors into a structured directory like docs/behavior-catalogs. This pipeline automates the generation and preservation of these catalogs, ensuring traceability between formal specs, generated tests, and behavior IDs throughout the module lifecycle.

Implementing the smallest code slice that satisfies a formal spec requires generating targeted unit tests first, then writing the minimal code to pass them. This pipeline orchestrates that flow, verifying the smallest implementation slice against the approved spec using pytest and ruff before auditing coverage.

Yes, this TDD pipeline requires specific directory structures, specifically docs/specs for formal specifications and docs/behavior-catalogs for durable behavior traceability. These directories ensure the automated workflow can correctly route specifications, enumerate behaviors, and maintain alignment before the final commit.

Yes, you can use a human-in-the-loop gate to validate behavior contracts before test generation. This pipeline explicitly includes a spec HITL gate, allowing developers to review and approve the formal specs and behavior contracts before automating unit test generation and code implementation.

Child skills like unit-test-gen and spec-coverage-audit are needed for TDD to handle specialized sub-tasks within the pipeline. unit-test-gen handles automated test creation from specs, while spec-coverage-audit verifies that the smallest code slice and generated tests fully align with the approved behavior contracts before committing.