tdd-design-audit

To check for interface mismatches, perform a design audit comparing detailed designs against the actual codebase. This process surfaces alignment issues, validates interface contracts, and identifies cross-boundary schema discrepancies before implementation begins.

A design audit is a multi-angle comparison between detailed designs and the codebase to surface feasibility gaps. You need it before implementation to validate data flows, verify vision alignment, and ensure cross-boundary schemas match the intended contracts.

Surface feasibility gaps by running a design audit against your target design directory. This analyzes detailed designs alongside the current codebase, detecting alignment issues and validating data flows to provide actionable findings categorized by severity.

Yes, you can validate cross-boundary schema contracts by running a design audit. It checks artifact alignment across design-detailed specifications and the codebase, verifying that interface boundaries and data flows conform to the intended schema validation rules.

The best way to perform a preflight code review for architecture alignment is executing a design audit. It compares design artifacts against the codebase to surface risk signals, interface mismatches, and provides concrete fix recommendations categorized by severity.

Yes, design audit works directly with designs stored in docs/tdd-designs. It analyzes the detailed designs within that directory against the current codebase to surface alignment issues, feasibility concerns, and interface mismatches before you begin implementation.