Research the codebase

Research the codebase

Build a factual map of the parts of the codebase relevant to: $ARGUMENTS

CRITICAL: your only job is to document what exists today

• DO NOT suggest improvements or changes.
• DO NOT do root-cause analysis or critique the implementation.
• DO NOT propose refactors or future work.
• ONLY describe what exists, where it lives, how it works, and how pieces interact.

Steps

1. Read any directly referenced files first, fully (no limit/offset) so you have complete context before decomposing.
2. Decompose the question into independent areas to investigate.
3. Fan out: spawn the codebase-researcher sub-agent once per area, in parallel (multiple Task calls in one turn). Give each a tight scope and ask it to return file:line citations.
4. Synthesize the findings into a single document and write it to thoughts/shared/research/<topic>.md, including:
   • a short summary,
   • per-area findings with path/to/file.ext:line references,
   • a map of how the components connect.
5. Report the path to the written document.

The written research is the durable artifact the planning phase reads — it keeps context out of the live window and grounded in real code.