architecture-validator

Architecture validation checks if plan.md contains required sections like Technical Context, Constitution Check, Project Structure, and Technology Stack. It verifies design artifacts exist and produces a readiness report to prevent incomplete designs from advancing into implementation.

Architecture validation requires plan.md to include Technical Context, Constitution Check, Project Structure, and Technology Stack sections. It also checks for relevant design artifacts like data-model.md, contracts, and research documents to ensure full alignment with the feature specification.

Architecture validation verifies the presence of design artifacts such as data-model.md, contracts, and research files alongside plan.md. It cross-references these artifacts with the feature specification to ensure technical context and project structure are fully aligned before implementation begins.

Architecture validation is designed for feature teams and technical validators needing evidence that required sections and artifacts exist. It outputs a structured validity report that guides architectural reviews and approvals by confirming documentation completeness.

Architecture validation automates readiness checks by scanning specs/*/plan.md files for mandatory sections and design artifacts. It generates a structured report confirming alignment with the feature specification, streamlining the design review and approval process without manual inspection.

Architecture validation fails reviews when plan.md lacks mandatory sections like Technical Context or Constitution Check, or when artifacts like data-model.md and contracts are missing. It outputs a structured report highlighting these gaps to prevent incomplete designs from advancing.