reverse-document

Name: reverse-document
Availability: InStock
Author: Traft

Generate design or architecture documents from existing codebases or prototypes.

33|8|Updated Mar 26, 2026

Search Tags:#code-analysis #documentation-generation #design-doc #architecture-doc #intent-clarification #reverse-documentation #prototype-analysis

Ready to run

npx skills add https://github.com/TraftG/opencode-game-studio --skill reverse-document-traftg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reverse-document
Source: https://github.com/TraftG/opencode-game-studio/tree/main/.opencode/skills/reverse-document
Command: npx skills add https://github.com/TraftG/opencode-game-studio --skill reverse-document-traftg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate design or architecture documents from existing implementation to formalize missing planning.

Core Features & Use Cases

Reverse-engineer design docs from code or prototypes to capture decisions, constraints, and intent.
Produce architecture ADRs or concept documents to guide future work.
Use case: Given a legacy module, generate a GDD section and ADR to document rationale and dependencies.

Quick Start

Invoke the command to reverse-document with a type and path, for example '/reverse-document design src/gameplay/feature'.

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 docs from existing code?▼

To generate design docs from existing code, invoke reverse-documentation with a type and path to analyze implementation and output a structured reverse-engineered document capturing decisions and dependencies.

What is reverse-documentation for legacy modules?▼

Reverse-documentation for legacy modules is the process of analyzing existing implementation to produce formal architecture or concept documents, capturing original constraints and intent when planning records are missing.

Can I produce architecture ADRs from a prototype codebase?▼

Yes, you can produce architecture ADRs from a prototype codebase by selecting the architecture type during reverse-documentation, which analyzes the code to formalize rationale and dependencies into structured records.

What's the best way to document missing intent in a system?▼

The best way to document missing intent is using reverse-documentation, which analyzes code or prototypes and explicitly tracks clarifications needed for missing intent within the generated design or architecture document.

Does reverse-documentation support concept analysis for prototypes?▼

Yes, reverse-documentation supports concept analysis for prototypes by allowing type selection, specifically generating concept documents that formalize system constraints and foundational planning from existing implementation.

When should I not use automated code analysis for documentation?▼

You should not use automated code analysis for documentation when the implementation lacks clear structural logic or when missing intent cannot be resolved through tracked clarifications, as output relies on analyzing existing code.