AI Documentation

Investigate a codebase and write documentation that explains how the system behaves rather than how the code is written. The reader is a product manager, founder, support lead, or new team member who needs an accurate mental model of the product without reading a single line of code.

This runs in the main conversation on purpose: the investigation depends on fanning out to code-explorer subagents, and a subagent cannot spawn subagents. Delegating the reading is what keeps enough context free to actually write well.

The two readers, and why the format is shaped this way

Every file you write serves two audiences at once: