design-review

To audit design documentation health, run a module design review that checks frontmatter presence, section coverage, cross-reference validation, and maintenance signals to produce a structured health report.

Cross-reference validation in design docs verifies that links between documents and modules resolve correctly. You need it when auditing traceability to surface gaps and prevent documentation drift from current project reality.

Checking frontmatter presence and section coverage involves scanning design docs to ensure required metadata fields and structural sections exist. The review produces actionable reports with prioritized recommendations for missing elements.

Yes, a design review identifies maintenance signals and gaps by evaluating design docs for completeness and cross-reference integrity. It delivers actionable remediation steps to align documentation with the current project state.

The best way to generate a structured health report is running an automated design review that evaluates frontmatter, structure, references, and maintenance signals, producing prioritized next steps for remediation.

Design documentation review works without external dependencies because it operates as a self-contained audit. It directly evaluates design docs for health, completeness, and cross-reference integrity to output structured remediation recommendations.