reverse-document

You can generate design documents from an undocumented codebase by analyzing source files to extract mechanics, state machines, and system interactions, then producing templated markdown outputs that capture the original design intent for review.

Creating design docs from a prototype folder involves analyzing the implementation to identify mechanics and formulas, surfacing unclear intent areas through targeted questions, and drafting formal concept documents or GDD sections using templates.

Yes, you can extract game mechanics and formulas into a GDD by analyzing prototype folders or individual files to identify system interactions and state machines, then generating templated markdown game design sections ready for collaborative writing.

Yes, the document generation workflow presents findings and drafts for your approval, and only writes templated markdown files into the repository when explicitly authorized during the collaborative write-out process.

The best way to onboard to an undocumented codebase is to reverse-engineer the implementation artifacts, extracting architecture patterns and system interactions to produce formal design documents and architecture records that capture the rationale behind the system.

You should use reverse-engineering to produce design documents when implementation exists without planning artifacts, making it hard to understand original design intent, architecture decisions, and missing edge-case behavior that need formalization.