content-audit

To check implemented assets against a game design document, run a content audit to parse markdown specs and glob-search asset directories, producing a detailed gap report comparing specified versus found item counts.

A content gap analysis for game development compares explicit content counts listed in markdown design documents against tallied game assets in source directories to detect scope creep and flag high-priority missing items.

You can track missing game assets by generating a gap report that extracts planned content counts from markdown specs, scans asset and source code directories, and flags high-priority discrepancies to prevent scope creep.

Yes, you can audit game content when design files are stored in markdown within the design/gdd/ directory and assets or source code are located in the assets/ or src/ directories, allowing direct spec-to-implementation comparison.

No, a content audit requires no external dependencies or components, operating directly on markdown specifications and file directories to parse planned content and output a gap report with priority flags.

The best way to generate a content gap report for a game project is to run an automated audit that parses markdown design specifications, tallies implemented assets via glob-search, and outputs a table of specified versus found items.