reverse-document

You can generate design documentation from existing code by analyzing mechanics, patterns, and formulas across specified file paths, then using an approval-gated workflow to write the final design doc.

In game development, reverse engineering documentation works backward from implementation to produce a game design document (GDD) by extracting mechanics, rules, state behavior, and system dependencies from existing prototypes.

Writing an architecture decision record from an existing codebase involves identifying patterns, coupling, and performance trade-offs from core system code, then asking intent clarification questions before generating the rationale.

You can convert a prototype into a concept document by extracting the core mechanic, emergent gameplay patterns, and feasibility insights to formalize what worked and what failed during prototype behavior.

Generating design docs requires answering intent clarification questions before writing the rationale portion of the document, ensuring the process codifies intended architecture rather than guessing design intent.

Analyzing code for reverse engineering documentation requires YAML frontmatter metadata plus argument parsing to process specified file or directory paths and extract implementation mechanics, patterns, and formulas.