reverse-document

You can generate architecture documentation from an existing codebase by reverse-engineering the implementation structure, identifying mechanics and decisions, and mapping them into standard templates like ADRs or design docs.

Creating a Game Design Document from prototype code involves parsing paths like 'prototypes/' or 'src/gameplay/', extracting mechanics and system rationale, and mapping those elements into a formal GDD template for review.

Writing an Architecture Decision Record for inherited legacy code requires reverse-engineering the existing implementation to identify historical mechanics and decisions, then mapping them into a ready-to-review ADR format.

Yes, you can reverse-engineer undocumented features by parsing the code structure to identify mechanics and decisions, then mapping them into standard concept doc templates to capture the missing rationale.

You should reverse-engineer code into design docs when working with inherited codebases, newly implemented features delivered without planning artifacts, or prototypes that need formal documentation for team onboarding and alignment.