What problem does it solve? Teams often ship features, inherit codebases, or prototype mechanics without ever writing design or architecture documentation, leaving the intent behind existing implementation undocumented and hard to maintain. ## Core Features & Use Cases - Reverse-engineered documentation: Analyzes source code or prototypes to extract mechanics, formulas, patterns, and dependencies, then drafts a GDD section, Architecture Decision Record, or concept document. - Intent clarification workflow: Asks targeted questions about why design decisions were made before drafting, separating intentional design from accidental behavior. - Approval-gated writing: Presents findings and drafts for review, writes the document only after approval, and flags follow-up work such as balance checks or missing edge cases. - Use Case: You inherited a combat system with no documentation. Run the skill on src/gameplay/combat/ to discover its mechanics and formulas, clarify design intent, and produce a reviewed GDD section marked as reverse-documented. ## Quick Start Ask the agent to run $ai-game-studio:reverse-document with a type (design, architecture, or concept) and a path such as src/gameplay/combat to generate a reviewed document from that code.
