What problem does it solve? Game teams often start building without a clear, measurable design document, causing scope creep, missing genre conventions, and downstream confusion in architecture and production. This Skill coaches a designer through producing a dense, traceable Game Design Document (GDD) that serves as the canonical source of design intent. ## Core Features & Use Cases - Three intent modes: Create a new GDD from scratch, Update an existing GDD against a change signal, or Validate a GDD against a structured checklist with an HTML/Markdown report. - Genre-aware scaffolding: Matches the game pitch against a game-type taxonomy (RPG, roguelike, fighting, platformer, and more) and loads genre-specific design sections and complexity requirements. - Traceability discipline: Enforces the chain from vision to pillars, core loop, mechanics, and development epics, with measurable mechanics and no engine-implementation leakage. - Use Case: A solo developer with a roguelike idea invokes the skill, confirms the game type, works through run structure and seed determinism sections, and ends with gdd.md, epics.md, and a decision log ready for the architecture phase. ## Quick Start Ask the AI to help you create a Game Design Document for your game idea using the gds-gdd skill.
