~aod-project-plan

You validate architecture documentation by running a validator against specs/*/plan.md files to confirm the presence of Technical Context, Constitution Check, Project Structure, and Technology Stack sections, ensuring alignment with the feature specification.

A plan.md pre-implementation review requires Technical Context, Constitution Check, Project Structure, and Technology Stack sections to be present and correctly aligned with the feature specification before development begins.

You check alignment by validating your architecture docs for required design artifacts like data-model.md, contracts, and research.md, verifying they match the corresponding feature specification in your specs directory.

Architecture validation generates a report indicating READY or NOT READY status and lists specific issues found in the plan.md file, helping you track missing sections or misaligned design artifacts before implementation.

You need architecture validation during pre-implementation reviews to ensure your plan.md across specs is complete, preventing downstream development issues caused by missing design artifacts or misaligned feature specifications.

If plan.md is missing Technical Context, the architecture validation marks the file as NOT READY and lists the missing section as an issue in the generated report, blocking the pre-implementation review process.