reverse-document

Generate a complete design or architecture document from your codebase with this intelligent tool.

23.7k|3.4k|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill reverse-document
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-document
Source: https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/reverse-document
Command: npx skills add https://github.com/Donchitos/Claude-Code-Game-Studios --skill reverse-document

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill bridges the gap between implemented code and necessary documentation, automatically generating design or architecture documents from existing codebases or prototypes.

Core Features & Use Cases

  • Reverse Engineering Documentation: Creates design documents (GDDs), Architecture Decision Records (ADRs), or concept documents by analyzing code.
  • Clarifies Intent: Asks targeted questions to understand the "why" behind the implementation, not just the "what".
  • Use Case: You've built a complex combat system without a design doc. Use this Skill to analyze the code, ask clarifying questions about your intent, and generate a formal GDD section.

Quick Start

Use the reverse-document skill to generate a design document for the src/gameplay/combat 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 design documentation from existing source code?

Generate design documentation from source code by using a reverse-engineering process that analyzes implementation details, identifies mechanics and patterns, and asks clarifying questions to ascertain developer intent before drafting formal documents.

What is reverse engineering in software architecture documentation?

Reverse engineering in software architecture documentation is the process of analyzing an existing codebase to extract implementation details and patterns, bridging the gap between built code and necessary formal design or concept documents.

Can I generate an ADR or GDD from a prototype codebase without prior docs?

Yes, you can generate an Architecture Decision Record (ADR) or Game Design Document (GDD) from a prototype codebase by analyzing the implementation details and clarifying developer intent to build the missing documentation.

How to document code mechanics when the original design intent is missing?

Document code mechanics when design intent is missing by analyzing the implementation to identify patterns, then asking targeted clarifying questions about the developer's goals to accurately capture the reasoning before drafting the document.

What is the best way to create architecture decision records for unrecorded systems?

The best way to create architecture decision records for unrecorded systems is reverse-engineering the existing code to analyze mechanics and patterns, asking clarifying questions to deduce intent, and then drafting the formal ADR.