reverse-document

Generate design, architecture, and concept documents from code and prototypes.

Updated May 24, 2026
One-click install
npx skills add https://github.com/LeKay/ai-game --skill reverse-document-lekay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-document
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/reverse-document
Command: npx skills add https://github.com/LeKay/ai-game --skill reverse-document-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of design or architecture documents from existing implementation, providing a solution to the challenge of documenting code and prototypes without initial planning.

Core Features & Use Cases

  • Design Documentation: Create game design documents (GDD) from implemented features.
  • Architecture Documentation: Generate Architecture Decision Records (ADR) for system architecture.
  • Concept Documentation: Formalize prototype mechanics into concept documents.
  • Use Case: When you need to document why and how a piece of code works after it has been implemented.

Quick Start

Use the /reverse-document command to generate a design document for the 'src/gameplay/magic-system' directory.

Frequently Asked Questions about reverse-document

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate architecture documentation from existing source code?

You can generate game design documents from implemented features by reverse-engineering the codebase to formalize mechanics and systems. This process requires code analysis and user clarification of design intent to structure the document accurately.

Can I create a game design document from an already implemented prototype?

Yes, you can create a game design document from an implemented prototype by reverse-engineering the mechanics. The process extracts formalized concept documents by analyzing the prototype code and clarifying the underlying design intent.

What is the best way to document why and how a piece of code works after implementation?

To generate architecture documentation from source code, you can reverse-engineer design documents by analyzing the implementation and clarifying design intent. This process extracts Architecture Decision Records and system specifications directly from your codebase.

Do I need initial planning documents to generate architecture decision records?

No, you do not need initial planning documents to generate architecture decision records. The reverse-engineering process automates document generation directly from existing implementations, solving the challenge of documenting code without prior planning.

How do I formalize prototype mechanics into concept documents?

To formalize prototype mechanics into concept documents, reverse-engineer the prototype implementation. This requires analyzing the code structure and clarifying user design intent to accurately extract and document the system features.