What problem does it solve? Writing a game design document for one system in isolation often produces contradictions with other systems, missing sections, and untestable requirements. This Skill walks you through each required GDD section collaboratively, gathering context from existing design docs first so the result stays consistent with the rest of the project. ## Core Features & Use Cases - Guided Section Cycle: Walks through Overview, Player Fantasy, Detailed Design, Formulas, Edge Cases, Dependencies, Tuning Knobs, and Acceptance Criteria with a draft-approve-write loop per section. - Context Gathering: Reads the game concept, systems index, entity registry, and dependency GDDs before designing, surfacing locked cross-system facts and past failure patterns. - Retrofit Mode: Fills only missing or placeholder sections of an existing GDD without overwriting completed content. - Specialist Delegation: Consults roles like systems-designer, creative-director, and qa-lead for formulas, fantasy framing, and testable acceptance criteria. - Use Case: After mapping your game's systems, run it on the movement system to produce a complete, registry-consistent GDD at design/gdd/movement.md with formulas and Given-When-Then acceptance criteria. ## Quick Start Ask the AI to design the movement system GDD using the design-system skill and approve each section as it is drafted.
