retrofit-existing

You can generate design documentation from an existing codebase by analyzing a target module to retroactively produce draft specifications, designs, and decisions that capture the current implementation for review.

Retrofitting framework documentation is the process of creating formal specs and designs for existing code. You need it when a codebase lacks documentation but seeks gradual adoption into a formal documentation structure.

You can document undocumented architectural decisions by analyzing existing implementation code to surface hidden choices, producing formal artifacts that reference the original code for ADR or DES documentation.

Yes, you can create a feature spec from an existing module without rewriting code by running a retrofit-spec command that analyzes the implementation and outputs a draft specification capturing current requirements and scope.

Prerequisites for retrofitting specs include having existing implementation code available and an available retrofitted spec structure to ensure the generated artifacts align properly with the documentation integration process.

Yes, retrofitting documentation works for codebases seeking gradual adoption by aligning existing code with a documentation structure, producing specs and designs that guide integration and ease future changes.