Research Codebase
Conduct comprehensive codebase research using parallel sub-agents.
Process
- •
Read mentioned files first
- •Read any files the user references FULLY (no limit/offset) before spawning tasks
- •This ensures you have necessary context before decomposing the question
- •
Decompose research question
- •Break into composable, independent research areas
- •Identify components, patterns, concepts to investigate
- •Create TodoWrite research plan with specific investigation items
- •
Spawn parallel sub-agents
- •Use
codebase-locatoragents to find relevant files and directories - •Use
codebase-analyzeragents on promising findings for deep dives - •Use
codebase-pattern-finderfor finding similar implementations or examples - •Run multiple agents in parallel for efficiency
- •Use
- •
Wait for ALL sub-agents, then synthesize
- •Prioritize live codebase findings over thoughts/ documentation
- •Include file paths and line numbers for all references
- •Highlight patterns, architectural decisions, and design rationale
- •
Generate research document
- •Output path:
thoughts/shared/research/YYYY-MM-DD-<description>.md - •Use template from
assets/research-template.md - •Add GitHub permalinks if on main branch or pushed to remote
- •Output path:
- •
Present findings to user
- •Summarize key discoveries
- •Highlight anything surprising or noteworthy
- •Note any open questions or areas needing further investigation
Path Handling
When referencing thoughts/ paths from search results, normalize them:
- •
thoughts/searchable/allison/...→thoughts/allison/... - •
thoughts/searchable/shared/...→thoughts/shared/...