tdd-implementation-audit

To audit code for TDD design drift, you verify completed implementations against design.md and detailed-design.md. This process checks scope coverage, interface fidelity, and test strategy alignment, ultimately generating an implementation-audit.md artifact that highlights gaps and deviations across all project phases.

The best way to verify implementation fidelity is by running a comprehensive end-to-end audit across your docs/tdd-designs directory. This checks that module structures, public APIs, and data flow match the detailed design, detecting any unintended additions or behavioral drift that occurred during phased development.

Yes, you can validate your test strategy by auditing the completed implementation against the design artifacts. The audit specifically confirms whether the test coverage and strategies described in your design documents were actually implemented and executed across the codebase.

You generate a gap analysis report by auditing the final codebase against your design specifications. The audit examines scope, interfaces, and tests to identify missing items and deviations, automatically producing an implementation-audit.md artifact summarizing all findings and recommendations.

Yes, the audit specifically targets designs stored under the docs/tdd-designs directory. It loads and verifies these design artifacts during a preflight phase to prepare for a comprehensive scope and interface fidelity check across the entire project.