reverse-document

You can generate design documentation from an undocumented codebase by analyzing existing source files and prototypes to extract technical patterns, mechanics, and architecture decisions into formal documents.

Yes, you can automatically create a Game Design Document by analyzing gameplay code to extract mechanics, formulas, and state machines into a structured formal document.

The best way to reverse-engineer architecture decision records is to analyze your source code to identify existing technical patterns and design decisions, then formalize them into structured documentation.

You can convert an experimental prototype into a concept document by analyzing the prototype codebase to formalize its implementation details and maintain the original project vision.

Yes, generating design docs from code requires read access to source files so the analysis can accurately match technical reality with design intent through iterative clarification.

You should use reverse-engineering to generate architecture documentation when you inherit undocumented systems or when existing documentation lags behind your current implementation.