What problem does it solve? Game prototypes often ship working code with zero documentation, leaving teams unable to explain architecture, onboard new members, or preserve design intent. This Skill reverses the traditional document-then-build flow by scanning an existing codebase and producing the human-readable design documentation that should have existed from the start. ## Core Features & Use Cases - System Detection and Mechanics Extraction: Scans code for fingerprints of movement, combat, inventory, UI, audio, save, AI, and other game systems, then extracts mechanics, tunable parameters, and design intent with VERIFIED/INFERRED/UNVERIFIED confidence markers. - Three Output Modes: Produces a reverse-engineered Game Design Document (design mode), an Architecture Decision Record with dependency maps and technical debt registers (architecture mode), or a game concept document extracted from a playable prototype (concept mode). - Dependency and Inconsistency Mapping: Maps cross-system dependencies, flags circular dependencies, orphaned code, missing systems, and contradictions between systems instead of hiding them. - Use Case: A game jam prototype is being promoted to a full project. Run the workflow in concept mode to extract the core loop, mechanics, scope assessment, and gaps, producing a concept document that guides full development. ## Quick Start Ask the assistant to document the existing game project at the repository root and generate a reverse-engineered design document from the code.
