docguard-guard

To validate CDD compliance, run a guard validation command that checks structural documentation, section completeness, and API surface traceability. This generates a severity-triaged report classifying issues as PASS, WARN, or FAIL to guide your remediation workflow before committing.

Documentation drift happens when implementation changes outpace updates to canonical docs, creating changelog gaps and misaligned drift-comments. Running a guard validator detects these breaks by assessing API surface traceability and structural completeness against the actual codebase.

Yes, you need a functioning DocGuard CLI or a local dev mode runner installed to execute the guard command. The validator requires detecting a CDD project root to execute its 19-validator suite and capture real output for triage.

The best way to triage documentation quality issues is to run a guard validation suite that categorizes findings by CRITICAL, HIGH, MEDIUM, and LOW severity. This produces an actionable remediation plan with targeted file and section fixes needed before merging.

You should run Spec-Kit validations after updating documentation or completing an implementation phase. This assesses structural documentation, section completeness, changelog gaps, and drift-comment alignment to ensure no CDD requirements are missing before committing.

Yes, running a guard validation command automatically generates a remediation plan for missing canonical docs. It maps validator failures to severity levels and produces specific next steps, including targeted file fixes and optional automated chaining to a fix skill.