What problem does it solve?
It helps you produce a complete, consistent game design document (GDD) for a single system by guiding you through every required section while pulling in cross-file context and dependency constraints.
Core Features & Use Cases
- Guided section-by-section GDD authoring: walks through the required sections incrementally so you can ship clarity without starting from scratch.
- Context-first design: reads the game concept, systems index, relevant registry facts, and dependency GDDs to prevent contradictions across your project.
- Retrofit-safe updates: identifies missing or placeholder sections and fills only what’s incomplete without overwriting existing content.
- Technical feasibility framing: checks engine/domain documentation (when configured) and surfaces constraints before you commit to design decisions.
- Approval gates and QA-minded output: uses explicit approval checkpoints per section and validates acceptance criteria are testable.
Quick Start
Use the /design-system movement command to generate a complete GDD for the movement system using your existing studio design files and dependency constraints.
