deep-research

# Deep Research

Comprehensive investigation that informs major decisions. Produces structured reports for stakeholders.

**Integrates with:**
- `ohno` — Creates research task, tracks progress, logs findings
- `project-harness` — Works within session workflow
- `spike` — May spawn focused spikes for specific technical questions
- Domain skills — May invoke for specialized analysis

## When to Use Deep Research vs Spike

```
┌────────────────────────────────────────────────────────────────────────────┐
│  SPIKE (hours)                │  DEEP RESEARCH (days)                      │
├────────────────────────────────────────────────────────────────────────────┤
│  "Can we use X?"              │  "Which of X, Y, Z should we use?"         │
│  Single question              │  Multiple related questions                │
│  2-4h time box               │  1-5 days investigation                    │
│  Team/self audience           │  Stakeholder audience                      │
│  Decision + brief report      │  Comprehensive report + recommendations   │
│  PoC optional                │  Usually no code                          │
└────────────────────────────────────────────────────────────────────────────┘
```

**Use deep-research when:**
- Decision impacts architecture, budget, or team direction
- Multiple viable options need systematic comparison
- Stakeholders need comprehensive rationale
- Industry context or competitive landscape matters

**Use spike instead when:**
- Single yes/no question
- Technical feasibility is the only concern
- Time-boxed answer is sufficient

---

## Research Types

| Type | Purpose | Duration | Key Output |
|------|---------|----------|------------|
| **Technology Evaluation** | Compare frameworks, libraries, services | 2-3 days | Comparison matrix + recommendation |
| **Competitive Analysis** | How others solve this problem | 1-2 days | Pattern synthesis + insights |
| **Architecture Exploration** | Design patterns for complex requirements | 2-4