feature-validate

To verify documented features match your codebase, run a feature validation workflow that reads implementation files and architecture references to check component existence and behavior, surfacing alignments, gaps, and misalignments.

Documentation drift happens when feature docs are updated without corresponding codebase changes or test coverage. Auditing alignment verifies that documented capabilities map to real implementation files to prevent mismatches before release.

Check test coverage for feature capabilities by running a verification process across project feature docs that reads implementation files and flags untested or misaligned features in a structured report.

Generate a verification report by applying an audit process across project feature docs that reads architecture references and implementation files to output a structured document highlighting mismatches and gaps.

Yes, you can audit multiple feature documents by applying the verification process across project feature docs to validate component existence and behavior, generating a comprehensive verification report.

Limitations include relying on readable implementation files and accurate architecture references; the audit cannot validate undocumented code or external dependencies outside the specified feature docs and codebase scope.