---

name: research-codebase description: research the codebase

Research Codebase

You are tasked with conducting comprehensive research across the codebase to answer user questions by spawning parallel sub-agents and synthesizing their findings.

CRITICAL: YOUR ONLY JOB IS TO DOCUMENT AND EXPLAIN THE CODEBASE AS IT EXISTS TODAY

• DO NOT suggest improvements or changes unless the user explicitly asks for them
• DO NOT perform root cause analysis unless the user explicitly asks for them
• DO NOT propose future enhancements unless the user explicitly asks for them
• DO NOT critique the implementation or identify problems
• DO NOT recommend refactoring, optimization, or architectural changes
• ONLY describe what exists, where it exists, how it works, and how components interact
• You are creating a technical map/documentation of the existing system

Initial Setup:

When this command is invoked, respond with:

CopyI'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.

Steps to follow after receiving the research query:

1. Read any directly mentioned files first:

   • If the user mentions specific files (tickets, docs, JSON), read them FULLY first
   • IMPORTANT: Use the Read tool WITHOUT limit/offset parameters to read entire files
   • CRITICAL: Read these files yourself in the main context before spawning any sub-tasks
   • This ensures you have full context before decomposing the research

2. Analyze and decompose the research question:

   • Break down the user's query into composable research areas
   • Take time to ultrathink about the underlying patterns, connections, and architectural implications the user might be seeking
   • Identify specific components, patterns, or concepts to investigate
   • Create a research plan using TodoWrite to track all subtasks
   • Consider which directories, files, or architectural patterns are relevant

3. Spawn parallel sub-agent tasks for comprehensive research:

   • Create multiple Task agents to research different aspects concurrently
   • We now have specialized agents that know how to do specific research tasks:

   For codebase research:

   • Use the codebase-locator agent to find WHERE files and components live
   • Use the codebase-analyzer agent to understand HOW specific code works (without critiquing it)
   • Use the codebase-pattern-finder agent to find examples of existing patterns (without evaluating them)

   For web research (only if user explicitly asks):

   • Use the web-search-researcher agent for external documentation and resources
   • IF you use web-research agents, instruct them to return LINKS with their findings, and please INCLUDE those links in your final report

   The key is to use these agents intelligently:

   • Start with locator agents to find what exists
   • Then use analyzer agents on the most promising findings to document how they work
   • Run multiple agents in parallel when they're searching for different things
   • Each agent knows its job - just tell it what you're looking for
   • Don't write detailed prompts about HOW to search - the agents already know

4. Wait for all sub-agents to complete and synthesize findings:

   • IMPORTANT: Wait for ALL sub-agent tasks to complete before proceeding
   • Compile all sub-agent results
   • Prioritize live codebase findings as primary source of truth
   • Connect findings across different components
   • Include specific file paths and line numbers for reference
   • Verify all rpi/ paths are correct (task-specific files go in rpi/tasks/)
   • Highlight patterns, connections, and architectural decisions
   • Answer the user's specific questions with concrete evidence

5. Gather metadata for the research document:

   • Filename: rpi/tasks/TASKNAME/YYYY-MM-DD-research.md
     • First, find the task directory: ls rpi/tasks | grep -i "eng-XXXX"
     • If the directory doesn't exist, create: rpi/tasks/ENG-XXXX-description/
     • Format: YYYY-MM-DD-research.md where YYYY-MM-DD is today's date
     • Directory naming:
       • With ticket: rpi/tasks/ENG-1478-parent-child-tracking/2025-01-08-research.md
       • Without ticket: rpi/tasks/authentication-flow/2025-01-08-research.md

6. Generate research document:

   • Use the metadata gathered in step 4
   • Read the research template:

   Read({SKILLBASE}/references/research_template.md)

   • Write the document to rpi/tasks/TASKNAME/YYYY-MM-DD-research.md

7. Add GitHub permalinks: When referencing documents in rpi/, use the rpi permalink command to generate GitHub links:

   • Run rpi permalink rpi/tasks/TASKNAME/document.md to get the permalink

• Include this link in your final output for easy navigation

  For code references in the synclayer repo (if on main or pushed):

  • Get repo info: gh repo view --json owner,name
  • Create permalinks: https://github.com/{owner}/{repo}/blob/{commit}/{file}#L{line}

1. Update the user

   • Read the final output template: Read({SKILLBASE}/references/research_final_answer.md)
   • Respond with a summary following the template, including GitHub permalinks.

2. Handle follow-up questions:

   • If the user has follow-up questions, append to the same research document
   • Update the frontmatter fields last_updated and last_updated_by to reflect the update
   • Add last_updated_note: "Added follow-up research for [brief description]" to frontmatter
   • Add a new section: ## Follow-up Research [timestamp]
   • Spawn new sub-agents as needed for additional investigation
   • Continue updating the document

Response

Remember, you must respond to the user according to the output template at {SKILLBASE}/references/research_final_answer.md

GitHub Permalinks

When referencing documents in rpi/, use the rpi permalink command to generate GitHub links:

• Run rpi permalink rpi/tasks/TASKNAME/document.md to get the permalink
• Include this link in your final output for easy navigation

Markdown Formatting

When writing markdown files that contain code blocks showing other markdown (like README examples or SKILL.md templates), use 4 backticks (````) for the outer fence so inner 3-backtick code blocks don't prematurely close it:

Copy# Example README
## Installation
```bash
npm install example
```