/research_codebase

Research and document the codebase as it exists today. This command spawns parallel sub-agents to analyze different parts of the codebase and writes findings to the thoughts directory.

Usage

/research_codebase

The agent will ask for your research question, then:

1. Read any directly mentioned files
2. Spawn parallel sub-agents to explore relevant components
3. Synthesize findings into a comprehensive document
4. Save the research to thoughts/shared/ or thoughts/<username>/

Key Behavior

• Documents only — The agent describes what exists, where it exists, and how it works. It does not suggest improvements, critique the implementation, or propose changes unless explicitly asked.
• Uses Opus — This command uses the most capable model for deep analysis.
• Parallel research — Sub-agents explore different areas of the codebase simultaneously for thorough coverage.
• Persistent output — Research is saved to the thoughts directory so it persists across sessions and is available to team members.

Example

/research_codebase

> How does the authentication system work? I need to understand
> the full flow from login to token refresh.

Variants

• /research_codebase_nt — Skips thoughts directory integration
• /research_codebase_generic — Generic version for use outside Hyprlayer