deep-research

/deep-research — Conversational Deep Research

Deeply research a topic before making decisions. Works through phases with user checkpoints between each — you control the direction. Each layer of research is cross-referenced against the goal, prior findings, and codebase reality before presenting. Produces a research report, not a design doc. Use /new-plan after to turn findings into an implementation plan.

---

When to Use

• Exploring a new technology, pattern, or approach before committing to it
• Investigating how other tools/frameworks solve a problem you're facing
• Understanding the current codebase deeply before planning changes
• Comparing multiple approaches with trade-offs before choosing one
• Gathering context that will inform a future /new-plan or /agent-team
• Any question where "just try it" is too risky and you need data first

When NOT to Use

• You already know what to build — use /new-plan or /agent-team directly
• Simple factual question — just ask directly without invoking a skill

---

Core Principle: Research Before Presenting

Never present raw findings directly. Every piece of information goes through a validation layer before the user sees it:

Raw finding → Cross-reference against goal → Validate against prior research → Check against codebase → Assess confidence → THEN present

If you can't validate a finding, say so explicitly with the reason. Don't present unvalidated information as fact.

---

How It Works

Phase 1: Scope           → Define question, dimensions, success criteria
     ↓ checkpoint
Phase 2: Explore          → Broad research across all dimensions
     ↓ internal validation (DO NOT present raw findings)
Phase 2.5: First Pass     → Cross-reference, filter, assess confidence
     ↓ checkpoint (present validated findings only)
Phase 3: Analyze          → Deep dive on user-selected threads (ITERATIVE)
     ↓ validate each round against goal + prior context
     ↓ checkpoint per round (user can loop or advance)
Phase 4: Synthesize       → Final validation pass, compile report
     ↓ checkpoint (user can refine)