reverse-document

To generate architecture documentation from existing code, analyze the implementation to extract decisions and rationale, producing an Architecture Decision Record that captures the 'why' behind the codebase structure and intent.

Yes, you can automatically create a Game Design Document from gameplay source code by analyzing existing mechanics and implementation details to derive the original design rationale and structured intent.

The best way to document the 'why' behind an undocumented codebase is reverse-engineering the implementation to extract architecture decisions and mechanics, generating structured ADRs or GDDs for onboarding and maintenance.

Write an Architecture Decision Record for an existing core system by analyzing the implementation to identify architectural choices, then structuring the extracted rationale and design intent into a clear, documented record.

Yes, reverse-document works with both core systems and gameplay layers, applying code analysis across architecture layers to extract mechanics and decisions, generating either a Game Design Document or an Architecture Decision Record.