codebase-exploration

To map codepaths for subtask planning, trace execution paths from entry points through architecture layers and surface 5–10 key files. This structured exploration reduces ambiguity and provides a reusable record appended to ai-work.md.

Codebase discovery is the process of locating entry points, mapping architecture layers, and tracing a golden path to understand impact. It supports architecture mapping by outlining patterns and surfacing essential files for reasoning.

Document codebase exploration notes by outlining identified entry points, architecture layers, and key files into a reusable template. Append this structured exploration record to ai-work.md as a dedicated exploration-notes section.

Yes, codebase exploration works without external dependencies or components. It relies on a structured template to trace execution paths and identify target files, requiring only an existing codebase to analyze.

The best way to trace execution paths for pattern discovery is to locate public exports or route files, map call sites to understand impact, and trace one golden path through the architecture layers to surface essential files.

You should not use a structured exploration template for simple subtasks that require no architecture mapping or pattern discovery. It is designed for leads guiding complex subtasks that depend on identifying target files and tracing execution paths.