Skip to content

Research It

Evidence-backed options before building; read-only by default.

Evidence-backed options before building; read-only by default. This practice is a skill-mapped TTP: when, why, and which command—not a full copy of the skill. Open the skill to execute.

Premature commitment is expensive. Lightweight research (constraints, prior art, tradeoffs) before build avoids Gall’s-Law violations. When the repo has no stronger local constraint, prefer house defaults: React+Next on Vercel for web, Pulumi ESC+OIDC for secrets, Langfuse for LLM obs/evals.

When the situation matches the one-liner above and Orientation (or your project path) says this is the fire to touch now.

  • Invoke the skill; follow its safety rules
  • Keep one write owner; collect evidence before claiming done
  • Hand off to the next practice instead of boiling the ocean
  • Skip orientation when you’re lost
  • Spawn overlapping agents to “go faster”
  • Treat the practice as done without evidence

04-evidence-over-vibes, 08-vision-tied-goals

See also the handbook Sources & grounding bibliography.

research-it