project-to-prd

To generate a PRD from a code repository, you can reverse-extract product requirements from implementation evidence like code, docs, tests, and API surfaces. This reconstructs a current-state PRD suite based on actual project artifacts.

Reverse engineering a PRD from a codebase is the process of scanning implementation evidence to reconstruct product documentation. It distinguishes between verified evidence and unknowns to compile a depth-aware PRD suite for UI, services, and flows.

Yes, you can extract product documentation from an existing app by routing the repository through an automated scan and build workflow. The system scans evidence like routes and data models, then compiles the PRD without requiring manual code reading.

To reconstruct requirements from repo evidence when documentation is missing, scan the repository's code, tests, configuration, and data models. The workflow identifies critical evidence gaps and blocks PRD completion until enough reconstruction readiness is achieved.

Limitations of reverse extracting a PRD include blocking completion when critical evidence gaps remain in the repository. Additionally, the process focuses strictly on current-state documentation and avoids automatically proceeding into downstream planning or implementation tasks.