content-audit

To verify game design document specs against repository implementation, you can run a content audit that parses explicit counts and lists from GDD files and scans implementation assets via Glob and Grep to produce a structured gap table.

Identifying planned versus built content gaps requires reconciling GDD-specified content counts with actual implementation outputs, classifying the status of each system as COMPLETE, IN PROGRESS, EARLY, or NOT STARTED to highlight missing assets.

Yes, you can perform a targeted content inventory check for a single game system by running a focused verification, which scans implementation coverage and extracts explicit counts for that specific system rather than auditing the entire project.

File scanning during implementation coverage audits works by using targeted Glob and Grep patterns to locate likely level, scene, data, and content assets within the repository, then comparing those findings against extracted GDD specifications.

Content auditing requires no external dependencies, but it needs readable GDD files containing explicit counts or lists and a repository structure where implementation assets can be located through standard file scanning patterns.

A GDD gap analysis might show a system as COMPLETE if the file scanning patterns fail to match the actual asset naming conventions, causing the audit to miscount the implemented content inventory within the repository.