reverse-document

To generate design documentation from existing game code, use a reverse-documentation approach to analyze implemented source systems and capture mechanics, formulas, and state systems into formal GDD sections.

You can create architecture decision records for an inherited codebase by reverse-engineering core system code to extract technical patterns, tradeoffs, and structural decisions into structured ADRs.

Documenting emergent gameplay mechanics from a prototype requires converting prototype implementations into concept docs that capture core mechanics, technical feasibility insights, and design intent.

Reverse-documentation works for undocumented gameplay systems in game development by analyzing the implemented source code to clarify design intent and formalize captured mechanics through collaborative user input.

To capture technical decisions from a codebase lacking upfront planning docs, extract implemented patterns and emergent technical tradeoffs directly from the source code to synthesize structured architecture documentation.

You should avoid reverse-engineering code into design docs when the source implementation is heavily obfuscated or when the collaborative user input required to clarify design intent is unavailable.