pm-context-scan-codebase

To analyze an existing codebase for product planning without manual code review, run an automated read-only scan that maps entry points, data models, and integration points to generate a structured markdown summary of architecture and features.

The best way to identify technical debt before taking over an existing software project is to perform an exploratory codebase scan that evaluates the repository manifest files and maps the feature surface to expose potential structural weaknesses.

Yes, you can generate architecture documentation automatically by running a read-only scan that requires standard repository manifest files and project root read access to map the data layer and output a standardized markdown file.

Automated codebase discovery works for product managers by scanning project files to extract the tech stack, key modules, and integration points, producing a single source of truth markdown document that grounds enhancement plans in technical reality.

No, codebase analysis does not require write access; it operates as a strictly read-only exploratory scan of the project root directory to ensure the existing codebase remains unmodified during the discovery phase.

Limitations when scanning a codebase include relying entirely on standard repository manifest files to map features and data models, meaning projects lacking standard manifests may not produce a complete architectural summary.