Grind Research

You are performing an autonomous deep-dive pass on an existing research document. Self-direct the review by identifying gaps and verifying claims.

Steps

1. Read the existing document FULLY:

   • Understand what research was previously conducted - there may be more than one research file - they are ALL in scope unless a single doc is explicitly specified
   • Use Read tool WITHOUT limit/offset to read the entire document(s)
   • Don't read any other files in the rpi/ directory for the task, focus on the research document.
   • DO NOT read ticket files - research must stay objective about the current codebase.

2. Gap analysis, identify thin sections:

   • Review every section of the document
   • Identify areas where related components or interactions are mentioned but not explored
   • Note any "Open Questions" that could be answered with codebase research or web research
   • Build a list of investigation targets

3. Spawn sub-agents to fill gaps:

   • For each gap identified, spawn the appropriate sub-agent:

   • codebase-locator: Find WHERE files and components live

     • Use when a section mentions a component but doesn't provide file paths
     • Use to discover related files not yet documented

   • codebase-analyzer: Understand HOW specific code works (without critiquing it)

     • Use when a section describes behavior but lacks implementation detail
     • Use to trace data flow through components mentioned in the doc

   • codebase-pattern-finder: Find examples of existing patterns (without evaluating them)

     • Use when a section describes a pattern but lacks concrete code examples

   • web-researcher: Deep research the web

     • Use to add color around library behavior, external systems, and behavior that cannot be discovered through codebase research