reverse-document

To generate design docs from existing code, you analyze the current implementation to extract mechanics, patterns, and decisions, producing structured documents that capture the original intent and rationale for inherited codebases lacking formal planning.

Creating architecture decision records for unfinished features involves reverse-engineering the existing implementation and prototypes to extract dependencies and patterns, ensuring the generated ADR accurately documents the architectural rationale and current state.

Yes, you can reverse-engineer a prototype into a formal game design document by analyzing the existing codebase to formalize missing planning, extracting core mechanics and dependencies to align the documentation with the actual implementation.

Code analysis extracts architecture patterns by evaluating the existing implementation and prototypes to identify structural decisions and dependencies, translating these technical findings into structured documents that clarify the original design intent.

You need to reverse-document a codebase when you inherit undocumented code, work on unfinished features, or need to formalize prototypes into structured design documents and architecture decision records to align planning with implementation.

Reverse-documenting code requires no specific dependencies or components, allowing you to directly analyze existing codebases and prototypes to generate structured design documents and architecture decision records without additional environment setup.