reverse-document

To generate design documentation from existing game code, you analyze the implementation to extract mechanics, rules, formulas, and state behaviors, then formalize these patterns backwards into a structured game design document.

Reverse documentation for inherited codebases is the process of analyzing existing implementation behaviors and working backwards to produce accurate architecture or design docs that reflect actual code reality rather than guesswork.

You create architecture decision records by analyzing the codebase to identify technical patterns, coupling, serialization approaches, and performance constraints, extracting the trade-offs to formalize ADRs.

Yes, you can analyze prototypes to generate concept documentation that captures the core mechanic, emergent gameplay patterns, and feasibility insights by working backwards from the implemented prototype behavior.

Generating documentation from code requires interactive intent clarification, asking targeted questions about rationale before writing anything, ensuring asserted design decisions are confirmed by the user prior to repository writes.

A limitation of reverse documenting code is identifying unclear intent areas where the rationale behind implementation choices is ambiguous, requiring structured argument parsing and explicit user confirmation before finalizing docs.