reverse-document

Generate design docs from existing source code by reading local project artifacts, extracting behavior and patterns, and drafting a document that captures current behavior, assumptions, and edge cases. The process identifies unclear intent and asks clarifying questions before writing.

Reverse-engineering an API module into architecture documentation involves analyzing the implementation folder to extract behavior, identify patterns, and produce a structured document covering current behavior, edge cases, and technical decisions. Uncertain areas are surfaced through targeted questions before finalizing.

You can reconstruct architecture decision records from an existing codebase by analyzing source code and project artifacts to derive technical decisions. The workflow extracts behavior and assumptions, preparing a draft with clarifying questions before any write action.

Document CLI workflows when original planning docs are missing by reading local project artifacts to extract behavior and patterns. The process identifies unclear intent, drafts a concept note capturing current behavior, and asks targeted questions before finalizing.

Reverse documentation works for analyzing migrations and UI behavior by reading local project artifacts to extract behavior, identify patterns, and prepare a draft document. It captures current behavior, assumptions, edge cases, and follow-up work before writing.

A limitation of reverse-engineering code into documentation is that intent may remain unclear from implementation alone. The process requires reading local project artifacts and depends on asking clarifying questions to surface uncertain areas before drafting final design documents.