content-audit

To compare your game design document against implemented assets, run a content audit that parses explicit content counts from GDDs and scans matching project directories to generate a gap table highlighting missing game content.

Gap analysis for game development requirements validation is the process of identifying mismatches between planned GDD content and actual implemented assets, preventing design drift by quantifying missing features and flagging high-priority gaps for execution.

Yes, you can run a content audit on a single game system instead of the full project. The skill supports flexible scope, allowing targeted verification for one system or full studio-wide validation across all implemented game assets.

To identify high-priority missing content for a vertical slice, execute a requirements validation audit that compares GDD-specified counts against scanned asset directories and prioritizes gaps critical to MVP systems for immediate development focus.

The content audit uses Glob and Grep file scanning to verify implemented game content against design documents. It requires your GDD to contain explicit content counts or lists and your project assets to be accessible via standard directory structures.

The best way to get a quick summary of design drift without a full report is to use the optional summary-only output mode. This lightweight audit mode provides a high-level overview of gaps between GDD specifications and actual built content.