recipe-reverse-engineer

You reverse-engineer a PRD from an existing codebase by initiating a discovery workflow that maps source units and dependencies to produce formal product requirement documentation artifacts.

The best way to create design docs for undocumented software projects is reverse-engineering the codebase to map source dependencies and generate traceable documentation artifacts through reviewer-guided revisions.

Yes, you can map codebase dependencies to traceable documentation automatically by running a reverse-engineering workflow that aligns discovered source units to formal PRD and design doc artifacts.

Yes, reverse-engineering documentation includes reviewer-guided revision loops that verify scope mapping and refine generated PRD and design docs to ensure complete stakeholder alignment.

You need to reverse-engineer PRD and design docs from source code during codebase discovery, documentation updates, or project review phases to accelerate planning and achieve stakeholder alignment.

Generating PRDs from code discovery alone may miss implicit business context, requiring reviewer-guided revisions and verification loops to ensure reverse-engineered documentation accurately reflects stakeholder intent.