design-review

You can check design doc feasibility by running an automated evaluation that highlights missing details, edge cases, and cross-system conflicts. It performs a phase-by-phase assessment of rules, formulas, and dependencies to identify impractical requirements before development.

Ensuring consistency in a game design document involves coordinating internal consistency checks against defined project standards. This evaluation identifies potential cross-system conflicts and missing details, verifying that rules and formulas align before handing the document to programmers.

Evaluating a game design spec requires a multi-phase review workflow that checks frontmatter presence and assesses overview, player fantasy, rules, and acceptance criteria. This surfaces gaps in dependencies and tuning knobs to confirm adherence to design standards.

No specific dependencies are required to evaluate game design documents. The automated review workflow operates independently, assessing frontmatter presence and document quality without needing external components or frameworks to function.

A complete game design document should include an overview, player fantasy, rules, formulas, edge cases, dependencies, tuning knobs, and acceptance criteria. The review evaluates these sections phase-by-phase to ensure frontmatter presence and full engineering readiness.