design-review

To validate design docs, provide the path to your design document. The review checks structure, cross-references, and terminology alignment, then outputs a structured verdict with blockers and optional recommendations.

Yes, it detects PRDs and routes them to the dedicated `/prd-review` path, while routing UX-related designs to `/ux-review` for specialized processing and generic design artefacts to standard review paths.

You can check concept docs, design bibles, flow specs, and other architecture artefacts. The process enforces required sections and cross-reference checks to ensure terminology alignment and implementability.

A design review outputs a structured verdict containing identified blockers, warnings, and optional snapshot guidance to support project governance and downstream team handoffs.

Cross-reference validation works by enforcing required sections and checking terminology alignment across design bibles and flow specs. It detects inconsistencies to ensure the artefact is complete and implementable.