content-audit

Find gaps between game design specs and implemented assets by scanning Markdown GDDs for enumerated content counts and using glob and grep to tally artifacts in your repository. The audit compares specified versus implemented levels, enemies, items, abilities, dialogue, and quests to generate a gap table.

A game content audit is a gap analysis comparing GDD-specified content counts against implemented repository artifacts. You need to run one when scattered design language and source assets must be converted into a prioritized, actionable gap report to identify missing or mismatched game content.

Yes, you can audit a single system like enemies or dialogue by running the audit with a specific system name argument. This single-system mode checks individual content categories, while the full-project mode scans all systems with an optional summary-only output.

The content audit works with game development projects using Markdown GDDs and repository asset or source folders. It applies glob and grep scans across design, assets, and src directories to approximate implemented counts for levels, enemies, items, abilities, dialogue, and quests.

Generate a dated gap report for missing game content by running a full audit scan, which extracts enumerated counts from Markdown design files and tallies found artifacts. It produces a per-system gap table with status flags and optionally writes a dated report file to your docs directory.

Using grep and glob for game asset inventory approximates implemented counts by pattern matching files across assets and source directories. It may flag unspecified counts as design gaps, but relies on directory structure and cannot assess runtime behavior or asset quality beyond file presence.