validate-design-coverage

Design coverage validation scans requirements documents, design documents, ADRs, and diagrams to confirm every REQ-* identifier is mentioned in design artifacts. It identifies gaps in components, APIs, data models, and diagrams so you catch incomplete designs before development begins.

Complete design coverage means a requirement is addressed across all necessary design dimensions: documented in architectural or design documents, represented in component diagrams, defined through APIs or data models, and traced in ADRs. The tool verifies these dimensions exist before signaling readiness.

Yes. The tool scans your requirements repository and design artifacts to produce a coverage audit report. It lists which REQ-* entries lack design mentions, reports coverage percentages, and identifies missing components, APIs, and data models so you can target remediation.

Traceability enforcement acts as a homeostasis gate: it signals design gaps early so incomplete architectures don't reach code phase. Gap reports and remediation recommendations let teams close coverage holes before starting implementation.

The tool produces gap reports listing uncovered requirements, coverage percentages per component or requirement, remediation recommendations, and outputs formatted for RAG indexing. Results highlight exactly which REQ-* entries need design attention and what's missing.

The tool is designed for requirements repositories and scans requirements docs, design documents, and ADRs. It expects REQ-* identifiers as the traceability anchor, matching them against design artifacts and architecture diagrams in your workspace.