design-system

Guided GDD authoring develops a system document section by section while reading project context, dependency GDDs, and engine references beforehand to preserve cross-system consistency across rules, formulas, and acceptance criteria.

Dependency analysis in game system design reads game concepts, system indexes, registries, and related GDDs to identify conflicts before design questions are asked. It is needed when designing systems like combat, economy, or AI in projects with established documentation.

You can retrofit missing or placeholder sections in an existing game design document without overwriting completed content. The workflow fills gaps in overview, player fantasy, rules, formulas, and tuning knobs while preserving your existing work.

Validate game mechanics and formulas using full, lean, or solo review modes that perform cross-system consistency checks, identify registry conflicts, and incorporate specialist feedback for mechanics, formulas, art, and QA to ensure testable acceptance criteria are met.

Collaborative GDD authoring works for solo developers through the solo review mode. While it supports specialist review agents for mechanics, formulas, art, and QA in team settings, solo mode allows individuals to validate rules and edge cases independently.

Retrofitting a game design document requires access to project context files, dependency GDDs, engine references, and architecture decisions. It is limited to projects with established design documentation and cannot generate missing dependencies or engine references that do not exist.