reverse-document

Generate design and architecture documentation from existing code and prototypes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill recovers missing design and architecture documentation from an existing implementation by analyzing code, prototypes, and system artifacts and translating them into readable planning documents and templates.

Core Features & Use Cases

  • Implementation Analysis: Reads code and prototype artifacts to identify mechanics, state machines, formulas, and architectural patterns.
  • Document Generation: Produces design doc sections (GDD), Architecture Decision Records (ADR), or concept documents based on implementation evidence and clarified intent.
  • Collaborative Workflow: Presents findings, asks targeted clarifying questions about intent, drafts documents using templates, and writes outputs to repository paths while flagging follow-up work.
  • Use Case: Reverse-engineer a combat system in src/gameplay/combat to create a GDD section that captures mechanics, formulas, and integration points.

Quick Start

Use the reverse-document skill by instructing /reverse-document design src/gameplay/combat to analyze the combat code and draft a GDD section.

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 analyze implementation artifacts to extract mechanics, formulas, state machines, and architectural patterns, translating them into structured documents like GDD sections or ADRs.

What is the best way to create an Architecture Decision Record from an existing implementation?

Creating an Architecture Decision Record from an implementation involves reverse-engineering code to identify architectural patterns and dependencies, then drafting a formal record that captures the recovered design evidence and clarifies intent.

Can I reverse engineer a game prototype to recover a missing Game Design Document?

Yes, you can reverse engineer a game prototype to recover a missing Game Design Document by analyzing prototype directories to extract mechanics, formulas, and integration points into a structured GDD section.

How do I extract state machines and architectural patterns from code for documentation?

Extracting state machines and architectural patterns from code requires analyzing the implementation to identify logical flows and structural dependencies, then mapping that evidence into formal design doc templates and suggested file paths.

Does reverse engineering code into design docs require manual input during the process?

Yes, reverse engineering code into design docs requires manual input through a collaborative workflow that presents findings and asks targeted clarifying questions about unclear intent items before drafting the final documents.