scaffold-review-design

To audit game design documents, you can run an automated review process that identifies unfilled sections, TODOs, and placeholder text while verifying synchronization between system index tables and corresponding files. This validates cross-references and highlights design gaps proactively.

Cross-reference auditing in game design documentation checks for broken links and circular dependencies between systems. It validates file existence within the design hierarchy to ensure structural integrity and consistent system mapping across the project.

You can check for broken links and circular dependencies by running an automated consistency validation process. This verifies file existence, validates system index synchronization, and audits cross-references within the design hierarchy to pinpoint structural inconsistencies.

Yes, the design audit provides advisory context based on common design pitfalls and genre conventions. It offers optional checks alongside completeness and consistency validation to help align your documentation with established best practices.

You should run a game design documentation review before a major design milestone. This generates a comprehensive report on gaps, unfilled sections, and inconsistencies, allowing you to address foundational errors proactively before development progresses.

The best way to validate system index synchronization is to use an automated consistency check that verifies system designs match across index tables and their corresponding files. This ensures data alignment and prevents broken cross-references within the hierarchy.