current-prd

To reverse-engineer a PRD from a codebase, you provide a local repository path and optional scope to trigger a global scan, module analysis, and final assembly, generating structured markdown reports for each phase.

Generating living documentation involves a three-phase process: scanning the technology stack and directory structure, analyzing module call hierarchies and database operations, and assembling these findings into a structured Product Requirements Document.

Yes, you can extract business rules and external integrations during the module analysis phase, which traces input/output contracts and database operations to map the functional requirements of your codebase.

Yes, this reverse-engineering approach applies to software repositories of varying sizes, allowing you to define an optional scope to focus the analysis on specific modules or let the global scan cover the entire codebase.

You receive phase-specific markdown reports for the global scan, module analysis, and the final assembled Product Requirements Document, providing clear living documentation mapped to the knowledge structure.

You should use reverse-engineering to generate requirements when you lack up-to-date documentation and need to turn existing code reality into maintainable specifications and structured PRDs for ongoing reference.