content-audit

To audit GDD content counts against implemented game assets, run a full system-wide scan comparing design/gdd specifications with inventoried assets to surface gaps. It verifies planned content versus built content across all systems.

Yes, you can check planned vs built content for a single game system by passing the specific system name as an argument. This executes a targeted single-system audit instead of scanning all GDDs.

A GDD content audit is a verification process comparing game design document specifications against actual implemented assets. Run an audit when tracking development progress and identifying missing content across systems.

To generate a summary overview of game content gaps without writing files, execute the audit using the --summary flag. This produces a high-level summary table showing planned versus implemented content counts.

Yes, the content audit automation supports globbing and grep operations for scanning design/gdd files to extract specified content counts. It inventories implemented assets to surface gaps between planned and built content.

The best way to track game design document progress against actual development is running audit automation that scans GDDs for content counts and inventories implemented assets. This surfaces gaps between planned and built systems.