reverse-document

Generate design and architecture documents from existing code and prototypes.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill reverse-document-rakhnianskii9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-document
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/reverse-document
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill reverse-document-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When code and prototypes exist without accompanying planning, this skill produces structured design or architecture documents to capture intent and decisions.

Core Features & Use Cases

  • Reverse-engineers implementation to generate design or ADR (architecture decision record) content from code, files, or prototypes.
  • Supports generating design documents (GDD sections), architecture documents (ADR), or concept briefs from prototypes.
  • Useful when inheriting a codebase, documenting why a system exists, or formalizing decisions after a prototype.

Quick Start

Use /reverse-document design src/gameplay/magic-system to generate a design document.

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 code?

You can generate architecture documentation from existing code by parsing the implementation and workflow notes to automatically produce structured documents like ADRs. This skill reverse-engineers codebases lacking formal planning docs to capture architectural decisions.

What is the best way to create a design doc from a prototype?

Creating a design doc from a prototype involves reverse-engineering the implementation to formalize intent and system design. This skill parses prototype files to generate structured Game Design Document sections or concept briefs automatically.

When do I need to reverse-engineer code into an ADR?

You need to reverse-engineer code into an ADR when inheriting a codebase that lacks formal planning docs or when formalizing architectural decisions after building a prototype. It captures why a system exists based on the actual implementation.

Can I document a codebase automatically if it lacks planning docs?

Yes, you can document a codebase automatically by parsing the existing code, prototypes, and workflow notes. This skill produces structured architecture and design documents to capture the original intent and decisions.

How do I start generating a design document from my source code?

You start generating a design document from source code by running the /reverse-document command with the document type and target directory. This parses the specified implementation files to produce the structured documentation.