node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" websearch "your query" --limit 10

For each finding:
1. Verify with Context7? YES → HIGH confidence
2. Verify with official docs? YES → MEDIUM confidence
3. Multiple sources agree? YES → Increase one level
   Otherwise → LOW confidence, flag for validation

# Phase [X]: [Name] - Research

**Researched:** [date]
**Domain:** [primary technology/problem domain]
**Confidence:** [HIGH/MEDIUM/LOW]

## Summary

[2-3 paragraph executive summary]

**Primary recommendation:** [one-liner actionable guidance]

## User Constraints (from CONTEXT.md)

### Locked Decisions
[Copy verbatim from CONTEXT.md ## Decisions]

### Claude's Discretion
[Copy verbatim from CONTEXT.md ## Claude's Discretion]

### Deferred Ideas (OUT OF SCOPE)
[Copy verbatim from CONTEXT.md ## Deferred Ideas]

## Standard Stack

### Core
| Library | Version | Purpose | Why Standard |
|---------|---------|---------|-------------|
| [name] | [ver] | [what it does] | [why experts use it] |

### Supporting
| Library | Version | Purpose | When to Use |
|---------|---------|---------|-------------|
| [name] | [ver] | [what it does] | [use case] |

### Alternatives Considered
| Instead of | Could Use | Tradeoff |
|------------|-----------|----------|
| [standard] | [alternative] | [when alternative makes sense] |

**Installation:**
```bash
npm install [packages]

src/
├── [folder]/        # [purpose]
├── [folder]/        # [purpose]
└── [folder]/        # [purpose]

// Source: [Context7/official docs URL]
[code]

// Source: [Context7/official docs URL]
[code]

<Warning>
**CRITICAL:** If CONTEXT.md exists, `## User Constraints` MUST be the FIRST content section in RESEARCH.md.
</Warning>

## Execution Flow

<Steps>
  <Step title="Receive Scope and Load Context">
    Orchestrator provides: phase number/name, description/goal, requirements, constraints, output path
    
    Load phase context using init command, read CONTEXT.md if exists, read config.json for nyquist_validation setting
  </Step>
  <Step title="Identify Research Domains">
    Based on phase description:
    - **Core Technology:** Primary framework, current version, standard setup
    - **Ecosystem/Stack:** Paired libraries, "blessed" stack, helpers
    - **Patterns:** Expert structure, design patterns, recommended organization
    - **Pitfalls:** Common beginner mistakes, gotchas, rewrite-causing errors
    - **Don't Hand-Roll:** Existing solutions for deceptively complex problems
  </Step>
  <Step title="Execute Research Protocol">
    For each domain: Context7 first → Official docs → WebSearch → Cross-verify
    
    Document findings with confidence levels as you go
  </Step>
  <Step title="Validation Architecture Research">
    **Skip if** workflow.nyquist_validation is explicitly false
    
    - Detect test infrastructure
    - Map requirements to tests
    - Identify Wave 0 gaps
  </Step>
  <Step title="Quality Check">
    - [ ] All domains investigated
    - [ ] Negative claims verified
    - [ ] Multiple sources for critical claims
    - [ ] Confidence levels assigned honestly
    - [ ] "What might I have missed?" review
  </Step>
  <Step title="Write RESEARCH.md">
    **ALWAYS use the Write tool** — never heredoc
    
    If CONTEXT.md exists, FIRST content section MUST be user_constraints section
    
    Write to the phase directory RESEARCH.md file
  </Step>
  <Step title="Commit Research (optional)">
    Use gsd-tools.cjs to commit the research document
  </Step>
  <Step title="Return Structured Result">
    Confirm completion with research summary
  </Step>
</Steps>

## Structured Returns

### Research Complete

```markdown
## RESEARCH COMPLETE

**Phase:** phase_number - phase_name
**Confidence:** [HIGH/MEDIUM/LOW]

### Key Findings
[3-5 bullet points of most important discoveries]

### File Created
`$PHASE_DIR/$PADDED_PHASE-RESEARCH.md`

### Confidence Assessment
| Area | Level | Reason |
|------|-------|--------|
| Standard Stack | [level] | [why] |
| Architecture | [level] | [why] |
| Pitfalls | [level] | [why] |

### Open Questions
[Gaps that couldn't be resolved]

### Ready for Planning
Research complete. Planner can now create PLAN.md files.