reverse-document

Generate design documents or architecture decision records from existing codebases.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill reverse-document-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-document
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/reverse-document
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill reverse-document-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams turn existing implementations into formal planning documents (design docs, architecture ADRs, and related artifacts) by analyzing code and prototypes to generate missing documentation, reducing rework and alignment gaps.

Core Features & Use Cases

  • Analyze code bases and prototypes to extract architectural decisions, interfaces, and rationale.
  • Generate design or architecture documents (GDDs, ADRs, prototype concepts) that reflect what the implementation does.
  • Use cases include onboarding new engineers, documenting legacy features, and aligning stakeholders on system rationale.

Quick Start

Run /reverse-document design src/gameplay/system to generate a design document from the codebase.

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 documents from existing source code?

Generate design documents from existing source code by applying the reverse-document skill to analyze your codebase or prototypes and extract implemented behavior, interfaces, and rationale into formal GDD artifacts.

What is the best way to create architecture decision records for undocumented features?

Create architecture decision records for undocumented features by analyzing implemented code to reverse-engineer architectural decisions and automatically produce formal ADRs reflecting the original system rationale.

Can I extract architectural rationale from a legacy codebase for onboarding?

You can extract architectural rationale from a legacy codebase for onboarding by analyzing the existing implementation to identify formal architectural decisions and generate missing design documents that align new engineers.

How to document legacy code by reverse-engineering architecture?

Document legacy code by reverse-engineering architecture through reading the implementation to identify interfaces and design decisions, producing formal design documents or architecture decision records that capture system behavior.

Does reverse-document work with partially documented prototypes?

Yes, reverse-document works with partially documented prototypes by reading the codebase to analyze implemented behavior and generating complete design or architecture documents that fill the missing documentation gaps.

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

You should not use automated code analysis for design documentation when the implementation lacks clear architectural intent, as reverse-engineering reflects implemented behavior rather than forward-looking design rationale.