reverse-document

To generate design docs from existing code, use a tool-driven approach to read your codebase, discover mechanics or architectural patterns, clarify intent via questions, and produce a draft for approval before writing.

Creating architecture decision records from a prototype involves analyzing the existing implementation to extract patterns and trade-offs, clarifying unclear intent, and generating a structured ADR draft for review.

Yes, you can document gameplay mechanics and ECS patterns without starting from scratch by reverse-engineering existing code to discover formulas and architecture, then generating a GDD-style design document.

Reverse documentation clarifies the original intent of unclear code by identifying ambiguous areas during codebase analysis and asking targeted questions to ensure the generated design or architecture documents capture the correct reasoning.

A limitation of generating concept docs from prototypes is that the process requires structured discovery and tool-driven file reading; if the prototype code lacks clear mechanics or patterns, the generated documentation may be incomplete.