review-design

To validate a design document against requirements, cross-reference setup.yaml, dev-design, and dev-investigation to surface alignment gaps and verify all criteria are addressed. This systematic design review ensures artifacts reflect investigation findings.

Tracing design decisions back to source requirements requires anchoring validation on the SSOT described in setup.yaml. The review process outputs structured decision summaries and updates design-document review sections to ensure full traceability.

Performing a design review across multiple target repositories involves loading setup.yaml inputs and applying the validation workflow to each. The process produces structured review outputs under docs/{target_repo}/review-design/ for each repository.

Yes, you need a setup.yaml file to automate design validation because it serves as the SSOT for requirements and specifies the target repositories. The validation workflow loads setup.yaml to verify design artifacts meet functional criteria.

If dev-design artifacts don't match prior investigation findings, run a design review to cross-reference dev-investigation and surface alignment gaps. The workflow updates the design-document review sections to ensure artifacts meet non-functional criteria.

Yes, you can use this design review approach to check if non-functional requirements are addressed in your architecture. The validation workflow verifies both functional and non-functional criteria are met by cross-referencing setup.yaml and design artifacts.