reverse-document

Generate design documents by reverse-engineering code and prototypes.

10|2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/wanghaisheng/OpenAgenticGame-Studios --skill reverse-document-wanghaisheng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reverse-document
Source: https://github.com/wanghaisheng/OpenAgenticGame-Studios/tree/main/refenrece/skills/reverse-document
Command: npx skills add https://github.com/wanghaisheng/OpenAgenticGame-Studios --skill reverse-document-wanghaisheng

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 essential documentation, automatically generating design, architecture, or concept documents from existing code or prototypes.

Core Features & Use Cases

  • Reverse Engineering Documentation: Analyzes code to infer mechanics, patterns, and intent.
  • Automated Document Generation: Creates GDD sections, ADRs, or concept documents based on implementation.
  • Use Case: You've built a complex combat system but never wrote a design doc. Use this Skill to analyze the combat code and generate a draft GDD, asking clarifying questions about your original intent.

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?

To generate design documentation from source code, you can analyze implementation details to infer mechanics and patterns, ask clarifying questions about intent, and draft GDD sections or concept documents using specified templates and output paths.

Can I automatically create an architecture decision record by reverse engineering a prototype?

Yes, you can create an architecture decision record (ADR) by reverse engineering a prototype. The process analyzes your existing code to infer mechanics and formulas before drafting the ADR based on the implementation.

What is the best way to write a game design document for a combat system I already built?

The best way to write a game design document (GDD) for an existing combat system is reverse engineering the code to infer patterns, answering clarifying questions about original intent, and generating draft GDD sections automatically.

Does this code analysis approach work for generating concept documents and ADRs without manual writing?

Yes, this code analysis approach works for generating concept documents and ADRs without manual writing. It bridges the gap between implemented code and essential documentation by automatically drafting based on inferred mechanics and intent.

How to reverse engineer mechanics and formulas from an existing codebase into documentation?

To reverse engineer mechanics and formulas into documentation, analyze the implementation details of your codebase, infer the underlying patterns, and draft the documentation using specified templates and output paths.