tdd-validation

TDD validation checks for mandatory sections, verifies MVP definitions, and ensures risks have mitigations. This structured process confirms the Technical Design Document is populated and ready for implementation.

You need TDD validation during pre-implementation reviews, PRD-to-SDD handoffs, and code review pipelines. Running it at these milestones ensures architecture alignment and verifies readiness before committing development resources.

Yes, TDD validation cross-checks your document against ARCHITECTURE.md and the CODEBASE. This architecture alignment verifies compatibility, ensuring the proposed design integrates seamlessly with your existing technical structure.

A TDD validation report includes structured checks verifying that MVP items are explicitly defined and that identified risks have corresponding mitigations. It outputs a standardized readiness assessment for code review pipelines.

Validating TDD structure during a PRD-to-SDD handoff involves scanning the document to ensure all mandatory sections exist and are properly populated. This structured validation prevents incomplete designs from reaching implementation.

A completed PRD is typically needed to validate a Technical Design Document because the validation process checks MVP status and architecture alignment. The PRD provides the foundational requirements needed to verify TDD readiness.