What problem does it solve? Teams often ship features, prototypes, or entire systems without writing design or architecture documentation first, leaving the intent behind the code undocumented and hard to maintain. This Skill works backwards from the implementation to produce the missing planning documents. ## Core Features & Use Cases - Reverse-engineered documentation: Analyzes source directories or files to extract mechanics, formulas, patterns, and dependencies, then drafts a GDD section, Architecture Decision Record, or concept document. - Collaborative intent clarification: Asks targeted questions about why design decisions were made before drafting, so documents capture intent rather than just describing code. - Traceable output: Writes approved documents with reverse-documented metadata markers and flags follow-up work such as balance checks or missing edge cases. - Use Case: You prototyped a combat system without a design doc; run the Skill on src/gameplay/combat to produce a formal GDD section capturing mechanics, formulas, and clarified design intent. ## Quick Start Ask the assistant to reverse-document the combat code by running /reverse-document design src/gameplay/combat and answer its clarifying questions.
