game-reverse-document

To generate game design documentation from a codebase, this Skill scans your source code to detect systems like movement and combat, then extracts mechanics to produce design documents and architecture decision records. It traces every claim to concrete files and marks uncertain intent as [UNVERIFIED].

Reverse-engineering a game codebase for design docs means analyzing source code to automatically capture game intent, architecture, and systems. The process detects cross-engine mechanics and maps their interactions into a living design document, concept summaries, and tunable parameter lists.

Yes, you can extract game mechanics from indie-game projects across different engines. The workflow applies a three-phase scan to detect systems, map dependencies, and identify gaps, producing architecture ADRs and concept overviews directly from the source files.

The best way to document undocumented game architecture is running an automated reverse-engineering workflow that scans code, detects cross-system interactions, and enumerates dependencies. This produces a human-readable design document that captures intent and architecture without manual tracing.

Yes, the generated design doc traces every claim back to concrete source files. Requirements for the documentation include mapping cross-system interactions, enumerating tunable parameters and dependencies, and explicitly marking any uncertain intent as [UNVERIFIED] to ensure accuracy.

A limitation of reverse-engineering game code is that it cannot perfectly infer original design intent, marking uncertain mechanics as [UNVERIFIED]. It relies entirely on the existing source code, so missing or highly obfuscated files may result in incomplete system detection and gap identification.