tdd-plan-audit

To audit a TDD plan against design documents, run deterministic checks on a target design directory to verify task coverage, interface alignment, phase sequencing, and file existence between plan.md and design.md files.

A deterministic plan audit for software design identifies inconsistencies between plan.md and its design documents by running automated checks and surfacing actionable findings before coding begins.

You verify task coverage and interface alignment by running a plan audit that applies deterministic checks to your design directory, automatically surfacing gaps between planned tasks and the detailed-design.md specifications.

Yes, you can run a plan audit in spike or auto mode by passing optional flags to the target design directory, consolidating the deterministic checks and council review results into a final report.

The council-based review uses three expert personas to categorize deterministic audit findings and resolve design gaps between plan.md and design documents, producing a consolidated final report for review.

For a software design audit, you need a plan.md file and a design.md file in the target directory, with an optional detailed-design.md file to enable deeper interface alignment and phase sequencing verification.