content-audit

To verify GDD-specified content against shipped assets, parse design documentation for explicit content counts and lists, then scan the project's file system using glob and grep patterns to detect build gaps. This generates a deterministic gap report for production planning.

A content audit in game production is the process of checking whether design-specified content counts and lists are actually implemented in the code and asset tree. You need one during production, sprint planning, and design-to-implementation alignment to prevent design drift.

Perform a gap analysis by parsing GDD summary sections for content-count keywords, then running deterministic file discovery via glob and grep across relevant directories. This counts implemented scenes, characters, items, abilities, dialogue, and quests to report missing assets.

Yes, you can audit a single named game system instead of running a full project inventory. The content audit supports both system-wide verification across all systems and focused per-system checks to align design documentation with implemented assets.

No, the content audit requires no external dependencies or components to function. It relies solely on parsing design and GDD system documentation and performing deterministic file discovery to generate a gap report format.

File system search for game asset verification is limited to deterministic glob and grep pattern matching on implemented scene and asset files, meaning it relies on explicit content-count language in GDD documentation and cannot infer missing assets from implicit or undocumented design intent.