create-research

name	create-research
description	research the codebase
disable_model_invocation	true
disable-model-invocation	true

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, check the task artifact directory from your system prompt for documents like *research-questions*.md with ls -La (the directory may be a symlink - do NOT use regular ls or grep/glob tools). If you find one, read it and proceed with the contents as the research query.

If you see several, ask the user which one to proceed with before reading any of them.

If you do not know what the task artifact directory is from your system prompt, 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.

IMPORTANT: You may NEVER read ticket.md files or other files from the artifact directory which do not match the research-questions pattern above unless such a file is explicitly asked for by the user.

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 (docs, JSON, research questions), 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
   • DO NOT read ticket files - research must stay objective about the current codebase, not be influenced by what a ticket wants to build. The research questions already capture what needs to be investigated.
   • 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 that tracks 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
   • Use the codebase-pattern-finder agent to find examples of existing patterns

   For web research and researching libraries & dependencies (if applicable):

   • Use the web-search-researcher agent for external documentation and resources
   • You may see a library researcher tool. If you do, you should use this to answer any research questions about dependencies and libraries that are in scope for the research. If the tool is not present, do not mention it.
   • 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:

   • Combine related questions: Don't necessarily launch one subagent per research question. Group related questions that touch the same area of the codebase into a single subagent prompt. For example, if 3 questions are about how the daemon handles sessions, combine them into one codebase-analyzer call.
   • Aim for 2-6 well-scoped subagents rather than 1:1 question-to-agent mapping - this is not a hard rule, just guidance
   • 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 areas of the codebase
   • 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 .tasks paths are correct (task-specific files go in .tasks/)
   • Highlight patterns, connections, and architectural decisions
   • Answer the user's specific questions with concrete evidence

5. Gather metadata for the research document:

   • Filename: .tasks/TASKNAME/NN-research-DESCRIPTION.md
     • First, check the task directory in your system prompt. If you do not see it, find the task directory: ls -La .tasks | grep -i "eng-XXXX"
     • If the directory doesn't exist, create: .tasks/ENG-XXXX-description/
     • Format: NN-research-DESCRIPTION.md where NN is a zero-padded chronological index and DESCRIPTION is a 2-4 word kebab-case slug
     • Chronological indexing: ls -La the task directory, find the highest existing NN- prefix, and use the next number. First document = 01-, second = 02-, etc.
     • Directory naming:
       • With ticket: .tasks/ENG-1478-parent-child-tracking/02-research-parent-child-tracking.md
       • Without ticket: .tasks/authentication-flow/02-research-auth-flow.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 .tasks/TASKNAME/NN-research-DESCRIPTION.md

7. Note artifact paths: Artifact paths are automatically provided when you write artifacts. Include them in your final output.

   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}

8. Respond to the user according to the template

   • Read the final output template: Read({SKILLBASE}/references/research_final_answer.md)
   • Respond following the template exactly, include artifact paths if you have them.

9. 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

Document Style and Format

The research document should read as a technical explainer, not a file index. A reader should be able to understand how the system works from the document alone — file citations support the narrative, they don't replace it. Human readability is critical, but never at the expense of technical depth and thoroughness.

Writing and citation style

• Write each findings section as a cohesive explanation of how something works, with file/line citations woven in parenthetically
• Concept-first, not location-first: describe what something does, then cite where it lives — not the other way around
• Bullets are fine for listing fields, flags, or options, but each bullet should describe a concept, not just point at a file
• When multiple facts come from adjacent lines in the same file, use a range (e.g. file.ts:45-67) rather than citing each line individually
• Be thorough — include enough citations that a developer can trace every claim back to code
• BAD: - \src/app.ts:57` creates WorkosService/- `src/app.ts:58` creates S3Service/- `src/app.ts:59` creates JiraService`
• GOOD: "Services are module-level singletons created at startup in src/app.ts:57-80: WorkosService, S3Service, JiraService, LinearService, StripeService, and two Drizzle database handles."

Visual structure

• Use the right visual tool for the information:
  • Tables for comparisons, capability matrices, and structured data
  • Mermaid diagrams for object graphs, data flows, and architectural relationships
  • Inline code blocks for key type signatures, configurations, and API shapes
  • Code examples and pseudocode to illustrate patterns concretely
• Don't rely solely on bullet lists — mix prose, tables, diagrams, and code
• Technical depth and thoroughness must not be sacrificed for readability — do both

Code References section

• Should be very comprehensive — a developer should be able to navigate the entire researched area from this list
• It is okay to reference directories in addition to individual files
• Indicate coverage: note when the list is exhaustive for a given area vs. when it covers key files but others in the directory may also be relevant
• Group related files together

Testing patterns

• Document under each findings section how that component is currently tested
• Include test file locations, testing approach (unit/integration/e2e), mocking patterns, test fixtures and utilities used
• If there are no tests, say so explicitly — that's a finding

## Important notes: - Use parallel Task agents to maximize efficiency and minimize context usage - Focus on finding concrete file paths and line numbers for developer reference - Research documents should be self-contained with all necessary context - Each sub-agent prompt should be specific and focused on read-only documentation operations - Document cross-component connections and how systems interact - Link to GitHub when possible for permanent references - Stay focused on synthesis, not deep file reading - Have sub-agents document examples and usage patterns as they exist - **REMEMBER**: Document and Ask about what IS and WHY, not what SHOULD BE - **NO RECOMMENDATIONS OR IMPLEMENTATION SUGGESTIONS**: Only describe the current state of the codebase - **Testing patterns**: For each component area you research, document how it's currently tested (unit, integration, e2e). Include test file locations and patterns. The research template has a "Testing patterns" section under each component - always fill it in. - **File reading**: Always read mentioned files FULLY (no limit/offset) before spawning sub-tasks - **Critical ordering**: Follow the numbered steps exactly - ALWAYS read mentioned files first before spawning sub-tasks (step 1) - ALWAYS wait for all sub-agents to complete before synthesizing (step 4) - ALWAYS gather metadata before writing the document (step 5 before step 6) - NEVER write the research document with placeholder values - **Path handling**: Task-specific research goes in .tasks/ - Use `.tasks/ENG-XXXX-description/NN-research-DESCRIPTION.md` for task research

Response

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

You should include the following text after the section in the final answer template that says 'If you'd like, you can review the research document for completeness.':

There are N open questions that you should review, you can
- ask me to go find the answers for them
- provide the answers yourself
- tell me they are irrelevant and I'll remove them

Artifact Paths

When you write or edit documents in .tasks/, include the generated local file path in your final response. If the tool output includes additional artifact metadata, you may include it as well.

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:

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