reverse-document

To generate design docs from existing code, invoke reverse-documentation with a type and path to analyze implementation and output a structured reverse-engineered document capturing decisions and dependencies.

Reverse-documentation for legacy modules is the process of analyzing existing implementation to produce formal architecture or concept documents, capturing original constraints and intent when planning records are missing.

Yes, you can produce architecture ADRs from a prototype codebase by selecting the architecture type during reverse-documentation, which analyzes the code to formalize rationale and dependencies into structured records.

The best way to document missing intent is using reverse-documentation, which analyzes code or prototypes and explicitly tracks clarifications needed for missing intent within the generated design or architecture document.

Yes, reverse-documentation supports concept analysis for prototypes by allowing type selection, specifically generating concept documents that formalize system constraints and foundational planning from existing implementation.

You should not use automated code analysis for documentation when the implementation lacks clear structural logic or when missing intent cannot be resolved through tracked clarifications, as output relies on analyzing existing code.