Research Codebase

Conduct comprehensive read-only research across the codebase by spawning parallel sub-agents and synthesizing their findings into a structured document.

Your only job: document what exists

• DO NOT suggest improvements or changes unless explicitly asked
• DO NOT perform root cause analysis unless explicitly asked
• DO NOT propose enhancements, critique the implementation, or recommend refactoring
• ONLY describe what exists, where it exists, how it works, and how components interact
• You are creating a technical map of the existing system

When invoked without a query

Respond with:

I'm ready to research the codebase. Please provide your research question or area of interest, and I'll analyze it thoroughly by exploring relevant components and connections.

Then wait for the user's research query.

Research workflow

1. Read directly mentioned files first

If the user mentions specific files (docs, configs, TOML, JSON), read them FULLY before doing anything else. Use the Read tool without limit/offset parameters. Read these yourself in the main context, this ensures full context before decomposing the research.

2. Decompose the research question

• Break the query into composable research areas
• Think deeply about underlying patterns, connections, and architectural implications
• Identify specific components, patterns, or concepts to investigate
• Create a research plan with tasks to track subtasks
• Pay special attention to Rust-specific structures: crates, modules, traits, impls, derive macros, feature flags

3. Spawn parallel sub-agents

Create multiple agents to research different aspects concurrently. Use the specialized agents: