reverse-document

You can generate design documentation by reverse-engineering the codebase to extract mechanics, formulas, patterns, and dependencies. This process uses interactive intent clarification and template-based drafting to produce traceable design docs that capture implied system behavior.

The best way to create ADRs from existing code is reverse-engineering technical patterns to identify architecture decisions, coupling, constraints, and trade-offs. This formalizes why things were built a certain way, converting implied implementation choices into traceable records.

You convert prototype behavior into a concept doc by analyzing the prototype to extract mechanic and feel descriptions, capturing what worked, what failed, and feasibility insights. This clarifies implied intent and transitions prototype analysis into structured planning documentation.

Yes, you can extract game design document sections by analyzing source code to derive mechanics, values, state interactions, system dependencies, and edge cases. This reverse-engineering process requires interactive intent clarification to ensure the drafted GDD matches actual mechanics.

Yes, reverse-documenting an inherited codebase requires interactive intent clarification to accurately capture implied behavior behind current implementation. The process uses controlled writing with approval to ensure extracted mechanics, formulas, and patterns produce traceable documents that reduce tribal knowledge.