gspec-audit

To audit codebase specifications and find documentation drift, compare your gspec documents directly against the implementation to detect discrepancies and identify orphan capabilities. This process ensures your specifications accurately reflect the actual code.

The best way to detect unspecced features in a codebase is to run a specification audit that inspects your code and identifies orphan capabilities, which are features implemented in the code but not documented in your gspec files.

To generate feature PRDs for undocumented code capabilities, run an audit to detect orphan capabilities and draft new feature PRDs directly from the discovered discrepancies, ensuring all implemented features are properly documented.

You should run a codebase specification audit before a major release to ensure your gspec specifications accurately reflect the codebase, catch any unspecced features, and prevent documentation drift from reaching production.

You can synchronize gspec documents with your codebase by running an audit that analyzes the gspec documents, inspects the code, and generates feature PRDs for unspecced features to reconcile any detected discrepancies.