content-audit

To compare GDD content counts against implemented game assets, run an audit that parses design/gdd systems-index files for explicit counts and lists, then scans relevant file patterns via Glob and Grep to compute specified versus found gap tables.

You can run a targeted gap analysis for a single game system by passing the specific system name as an argument, which limits the file scanning and GDD extraction to that system for faster iteration instead of a full-project audit.

GDD-to-build inventory comparison is the process of extracting explicit content counts or enumerated lists from design files and comparing them against what exists in the project, needed when verifying levels, enemies, items, abilities, dialogue, and quests implementation.

Generate a prioritized content gap report by auditing GDD-specified content against implemented assets, which produces a gap table and flags HIGH PRIORITY systems based on MVP or Vertical Slice context and implementation status.

The content audit supports both modes: full audits write a dated report into the docs directory, while running with the summary flag prints the gap analysis results directly in chat for quick checks without file output.

Implementation verification of game design specs uses Glob and Grep to scan relevant file patterns across design and implementation directories, computing specified versus found gaps for content like levels, enemies, items, abilities, dialogue, and quests.