reverse-document

Generate design docs from an existing codebase by parsing implementation files to automatically derive formal structured markdown outputs like CDDs and ADRs. This reverse engineering process turns code into planning artifacts that capture architecture and decisions for review.

Reverse engineering code into ADRs and CDDs is the process of deriving formal architecture and design documentation from existing implementations. It produces structured markdown outputs that capture intent, constraints, and interfaces for projects with sparse documentation.

Yes, you can create architecture documentation for diverse project types including games, APIs, CLIs, web apps, SDKs, and data pipelines. The process parses codebases, prototypes, and artifacts across these formats to produce coherent design documents.

Document an inherited project with no existing design documents by running a command to derive a design doc from the source code. This captures the original implementation intent, constraints, and interfaces into a formal planning artifact for hand-offs and audits.

The best way to turn code into version-controlled planning artifacts is to automatically parse implementations and generate structured markdown design documents. This establishes a coherent narrative from implementation to formal documentation that can be reviewed and tracked.

No dependencies are required to reverse document your source code. The process works directly on your codebases, prototypes, and artifacts to produce structured markdown outputs without needing external libraries or environment setup.