reverse-document

Run the reverse-document skill with the design type and a path to your implementation, such as src/gameplay/combat/. It analyzes mechanics, formulas, and state machines, asks clarifying questions about intent, then drafts a GDD section for your approval.

It supports three types: design produces a game design document section, architecture produces an Architecture Decision Record, and concept produces a concept document from a prototype. The type is chosen based on what you are analyzing.

Yes, use the concept type with the prototype directory path. The skill identifies the core mechanic, emergent gameplay patterns, and technical feasibility insights, then drafts a concept document after clarifying your design intent.

No, it follows an approval-gated workflow. It presents findings, asks clarifying questions, shows the draft, and only writes the file after you explicitly approve the target path.

The document captures current behavior plus clarified intent, but sections may be incomplete where implementation is partial or intent was unclear. It flags follow-up work such as balance checks and missing edge cases rather than resolving them automatically.