Reverse

You can generate legacy documentation from an existing codebase by reverse engineering the source code to produce initial spec.md and architecture artifacts. This process extracts API endpoints, data models, and component structures to bootstrap requirements.

Code-to-doc reverse engineering is the process of analyzing a codebase to produce initial legacy documentation where docs are missing. It converts code into spec and architecture artifacts, establishing traceable links between the implementation and design outputs.

You extract API endpoints and data models for design specs by analyzing both backend and frontend code to scaffold requirements. This generates initial design artifacts like spec.md and arch-be.md or arch-fe.md to document the identified structures.

Yes, you can generate both frontend and backend architecture docs from code. The reverse engineering process targets both codebases to scaffold design artifacts, outputting arch-be.md for backend and arch-fe.md for frontend component structures.

When generated code documentation has incomplete sections, you should use reinforcement to fill the gaps and polish the outputs. The initial scaffolding provides a first-pass structure that requires review to complete missing details and establish full traceability.