reverse-document

To generate design documents from existing code, provide the document type (design) and the target codebase path. The tool reverse-engineers the implementation to extract intent and produce a structured GDD with source provenance.

Creating architecture decision records from a prototype requires specifying the architecture type and target path. It reverse-engineers the existing implementation to extract design rationales and populate structured ADRs with traceability links.

Yes, you can extract design intent and decisions from an undocumented codebase. The tool analyzes the given implementation path to identify architectural patterns and decisions, generating structured documentation with provenance for downstream reuse.

No specific dependencies are required to reverse-engineer code for documentation. You only need to provide the desired document type (design, architecture, or concept) and the target path to the existing codebase or prototype.

You need to generate concept notes from an implementation when you lack initial planning docs for a prototype. Providing the concept type and path allows the tool to extract intent and produce structured notes with source traceability.

Through code reverse-engineering, you can produce three types of documentation: design documents (GDD), architecture decisions (ADR), and concept notes. All generated docs include provenance linking them to source paths and components.