Verified:GitHub

reverse-document

Convert implementation code into design and architecture documentation.

Updated Apr 4, 2026

Search Tags:#documentation generation #codebase understanding #architecture decision record #reverse-engineering #prototype analysis #game design document #design intent clarification

Ready to run

npx skills add https://github.com/WindXRan/y3td --skill reverse-document-windxran

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reverse-document
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/reverse-document
Command: npx skills add https://github.com/WindXRan/y3td --skill reverse-document-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of missing or outdated design and architecture documentation by generating them directly from working code or prototypes, so teams don’t have to guess intent or behavior later.

Core Features & Use Cases

Reverse-engineer design intent: Extract gameplay mechanics, rules, formulas, state machines, progression, and edge cases from an implementation.
Create architecture decision records (ADRs): Identify technical patterns and capture the “why” behind decisions by analyzing code structure, coupling, and constraints.
Document prototypes as concepts: Convert prototype findings into concept documents that capture what emerged, what worked, and what didn’t.
Clarify before writing: Asks targeted questions about intent and ambiguous areas, then uses an appropriate template and writes the final document only after user approval.

Quick Start

Use the reverse-document skill to generate a design GDD by analyzing src/gameplay/magic-system.

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 an existing codebase?▼

To generate design documentation from an existing codebase, this Skill parses your implementation paths to extract mechanics, patterns, and state machines, then outputs a formalized template-based document after you confirm the clarified intent.

How do I create architecture decision records for inherited code?▼

To create architecture decision records for inherited code, this Skill analyzes code structure, coupling, and constraints to identify technical patterns and capture the reasoning behind past technical decisions.

Can I convert a feature prototype into a game design document?▼

Yes, you can convert a feature prototype into a game design document by analyzing the prototype implementation to extract gameplay rules and progression, capturing what emerged and what worked into a formalized concept document.

Does the documentation generation process require manual input before writing?▼

Yes, the documentation generation process requires manual input, as this Skill asks targeted clarifying questions about design intent and ambiguous areas, then writes the final document only after receiving your explicit approval.

What is the best way to document undocumented mechanics in a prototype?▼

The best way to document undocumented mechanics in a prototype is to reverse-engineer the implementation by extracting formulas, rules, and edge cases, then converting those findings into a structured concept document.

When should I not use automated reverse-engineering for design docs?▼

You should not use automated reverse-engineering for design docs if the codebase lacks clear extractable patterns, or if you cannot provide the necessary intent clarifications required to finalize the template-based document.