How

Explore the codebase to answer "how does X work?" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source code.

Use the available subagent tool for the steps below. All exploration and explanation is read-only. If subagents are unavailable, perform those steps directly.

Step 1. Assess complexity

If the scope is ambiguous, state your interpretation and explore. The user can redirect.

• Simple (a single module, a small utility, a narrow question such as "how does function X work"): no explorers. One explainer explores and explains in a single pass. Go to Step 2b.
• Complex (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): spawn parallel explorers first, then hand off to the explainer. Go to Step 2a.

When in doubt, take the simple path.

Step 2a. Explore (complex questions only)

Decompose the question into 2 to 4 exploration angles, each a distinct slice of the subsystem. Spawn the explorers in parallel.

Each explorer gets the prompt in references/explorer-prompt.md with its angle filled in. Then go to Step 3.

Step 2b. Direct explain (simple questions)

Spawn one subagent that explores and explains in one pass.

Build its prompt from references/explainer-prompt.md without the explorer-findings section. Go to Step 4.

Step 3. Synthesize (complex questions only)

Once all explorers have returned, spawn one subagent to synthesize their findings into one explanation.

Build its prompt from references/explainer-prompt.md with every explorer's findings filled in.

Step 4. Present

Present the explainer's output to the user. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it.

Output format

The explanation uses the sections defined in references/explainer-prompt.md, dropping any that do not apply: Overview, Key concepts, How it works, Where things live, Gotchas.