why
Why
Investigate the motivation and intent behind code. why answers what forces led to its shape.
Set each investigator's effort two steps below your own, and the synthesizer's effort one step below your own. If you do not know your effort, do not set it.
Every spawn is a general-purpose subagent that starts with a fresh context window and can call your MCP tools. Without them, the MCP-backed investigators and the synthesizer's citation spot-checks do not work. Investigators still shouldn't write anything.
Operating Posture
Operate as a careful, cautious, and precise investigator. Be honest about what you know vs what you're inferring. Read references/epistemics.md for the full confidence framework and phrasing guide. The synthesizer must follow it.
Step 1. Understand the Target and the Question
The target is usually a chunk of code, a pattern, a feature, or a named design decision. The question is usually a design rationale, a tradeoff, a motivating edge case, an external constraint, dead code, or a broad history sweep.
If the target is vague ("why do we do it this way?" with no clear referent), make your best guess from conversation context (open files, recent edits, cursor location, what was just discussed). State your interpretation briefly so the user can redirect if you're off, then proceed.