design-review

Reviewing a game design document for completeness involves identifying gaps and validating dependencies against design standards. You apply a phase-based review workflow to produce a structured verdict with blocking items and next steps.

Checking game design document consistency requires analyzing internal logic and implementability before development. A phase-driven review workflow validates dependencies and surfaces recommended revisions for stakeholders to address.

Running adversarial analysis on a game design document uses an optional phase during the review workflow to stress-test spec validation. This deeper analysis identifies potential implementation gaps and structural weaknesses.

Spec validation is needed before handing a design document to programmers to ensure implementability. It checks for completeness, internal consistency, and adherence to project design standards to prevent downstream development issues.

Yes, the design review workflow supports optional expert delegation in full mode for deeper analysis. This allows for comprehensive spec validation and more thorough identification of implementability gaps.

A game design document review report should include a structured verdict with blocking items, recommended revisions, and clear next steps. This ensures stakeholders understand the design's completeness and consistency status.