repo-discovery

Mapping a codebase surface involves analyzing the repository layout, root manifests, and build tooling to identify the stack, entry points, tests, and risk flags. This structured reconnaissance data guides initial scoping and pre-flight planning.

Codebase discovery is the process of executing minimal effective reconnaissance to map the real implementation surface, including boundaries and commands. You need it before deeper analysis or pre-flight planning to understand project scope without editing files or designing the solution.

You identify entry points and dependencies by applying reconnaissance to root manifests, directory structures, and common build tooling. This generates a scout report detailing files and risks to guide planning workflows.

Codebase reconnaissance does not modify files or design the solution. It strictly maps the implementation surface by identifying stack, boundaries, commands, tests, and risks to provide structured data for initial scoping.

Yes, codebase discovery is useful for pre-flight planning in conductor workflows. It provides structured reconnaissance data suitable for Scout Phase 1 to detail stack, entry points, files, and risks before deeper analysis.

Codebase reconnaissance is limited to mapping surface risks from root manifests and directory structures. It does not edit files or design solutions, meaning deeper architectural risks require subsequent analysis beyond this initial scoping phase.