Research Codebase

Document how the codebase works as it exists today, then write the findings to a dated research document. Self-contained: the only helper it needs ships in scripts/. It dispatches parallel sub-agents by default, falling back to sequential research only when your agent can't spawn them.

The one rule: describe, don't evaluate

Your job is to document, not critique. While researching:

• Describe what exists, where it lives, how it works, and how pieces interact.
• Do NOT suggest improvements, refactors, optimizations, or future work.
• Do NOT do root-cause analysis or flag problems.
• Do those things only if the user explicitly asks.

You are drawing a technical map of the current system.

Step 1 — Get the question

If no research question was given, ask for one and wait: