reverse-document

Generate design PRDs, ADRs, and concept documents from existing implementations.

70|42|Updated Mar 27, 2026

Search Tags:#workflow #documentation #code-analysis #design-doc #architecture-doc #reverse-documentation #intent-elicitation

Ready to run

npx skills add https://github.com/tranhieutt/software_development_department --skill reverse-document-tranhieutt

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill transforms undocumented implementations or prototypes into structured design, architecture, or concept documents by analyzing the existing code and surfacing intent before writing anything.

Core Features & Use Cases

Intent-first analysis: Mirrors the requested path to collect mechanics, dependencies, and trade-offs so documentation matches the actual implementation.
Template-driven drafting: Aligns design, architecture, or concept outputs with their respective templates and target folders after understanding context.
Collaborative checkpoints: Presents findings, flags unclear intent, and waits for approval before persisting any documents.
Use Case: Reverse-engineer combat logic into a PRD after prototyping or capture legacy core systems as ADRs for architectural clarity.

Quick Start

Start with /reverse-document design src/api/auth to begin documenting your combat implementation.

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 without prior specs?▼

To generate documentation from an undocumented codebase, analyze the existing implementation to extract mechanics, dependencies, and intent, then draft structured design PRDs or concept documents with user confirmation before saving.

What is reverse-documentation for legacy code architecture?▼

Reverse-documentation for legacy code is the process of analyzing existing implementations to surface architectural decisions and trade-offs, generating structured ADRs or concept documents to provide post-facto clarity for systems lacking original specifications.

Can I create architecture decision records from a prototype implementation?▼

Yes, you can create architecture decision records from a prototype implementation by reading the code to collect trade-offs and mechanics, flagging unclear intent, and waiting for your approval before persisting the finalized ADRs to their target folders.

What's the best way to document combat logic after prototyping?▼

The best way to document combat logic after prototyping is to mirror the requested path to collect mechanics and dependencies, align the extracted findings with a design PRD template, and draft the document after confirming the elicited intent.

Does reverse-documentation work for core systems and APIs without dependencies?▼

Yes, reverse-documentation works for core systems and APIs without external dependencies, reading the implementation directly to extract architecture decisions and intent before drafting template-driven concept documents or PRDs.

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

You should avoid automated code analysis for generating documentation when the implementation intent is completely obscured or unconfirmable, as the process requires collaborative checkpoints and user approval to ensure the drafted docs match the actual implementation.