Research It

Replace vibes with evidence: what exists, what fits this repo, what to do next.

When to use

• “What’s the best way to…?”, “research it”, vendor/API comparison, spike before build
• Ambiguous architecture choice before recon issue or fix-it
• Need external docs or in-repo prior art surveyed first

Workflow

1. Frame the question

   • Decision to make, constraints (stack, latency, cost, compliance, timeline), success criteria.

2. Search inward then outward

   • In-repo: existing packages, patterns, ADRs, prior PRs/issues.
   • External: official docs (WebFetch), reputable references; note versions/dates.
   • Don’t treat random blogs as authority over primary docs.