reverse-document

Generate design documentation from an existing codebase by reading the specified path, identifying technical patterns and dependencies, asking clarifying intent questions, and drafting with an appropriate template. The Skill writes the final design docs only after user approval.

Yes, you can create architecture decision records from existing source code. The Skill extracts technical patterns and constraints from implemented systems and formats them as ADRs to formalize undocumented architecture decisions.

The best way to document prototype behavior into reusable specs is to analyze the prototype code to identify core mechanic intent and emergent patterns. The Skill generates concept docs that capture feasibility insights from the existing prototype.

Yes, the reverse documentation process asks targeted clarifying questions before drafting. This collaborative intent clarification separates true design intent from accidental behavior in the codebase, ensuring accurate documentation before any output is written.

Reverse-document inherited undocumented systems by pointing the Skill at the code path. It identifies mechanics, rules, and formulas within the system, then drafts the missing documentation using an appropriate template for your review and approval.

Yes, you can use this for documenting shipped code lacking mechanics documentation. The Skill reverse-engineers implemented mechanics into a structured game design document format, capturing rules, formulas, and existing uncertainties from the codebase.