Odin Research

Use when the user asks "how does X work" and wants an architecture walkthrough of the code path or subsystem, including its gotchas. Don't use for tasks that require source or remote-system changes.

Use when asked why something works this way, for design rationale, a postmortem, a data-backed threshold, or a source-tiered evidence report. Not for current runtime behavior: use how.

Use when the user runs /scrape with a URL to extract page data and media through a browser and save assets with a manifest locally. Read-only. Not for any mutating page action.

Use when a user wants a readable, shareable HTML document of findings. Not for remote, credential, publish, deploy, or irreversible changes.

Use when researching a named library, framework, SDK, API, or service, or finding a migration guide. Not for codebase-internal research. Dispatch a scout agent.

Use when roadmap, plans, or docs may have drifted from code, or when restarting a stalled project. Not for PR doc sync: use docs-update.

Use when the user asks to research a topic and produce a thorough sourced report. Not for remote, credential, publish, deploy, or irreversible changes.

Use when starting or scaffolding a codebase or service, migrating, refactoring, or picking language, framework, or dependency, or latest, LTS, or modern way. Not for remote or irreversible changes.

Use when a claim needs checking both ways, "fact-check this", or an artifact or HTML document needs claims verified and corrected in place. Modes: claim, artifact. Not for measuring: use verify-this.

Use when a genealogical identity or relationship needs correlation, conflict analysis, and negative-search proof. Not for non-genealogical identity proof.

Use when a research-backed answer requires codebase and docs investigation, reading many files, or a wide survey. Not for file edits, diffs, or patches, nor remote-system changes.

Use when the user asks to summarize a set of documents, identify themes and conflicts across multiple files, or synthesize internal docs. Not for single-document summaries or non-text sources.

Use when a bug, integration failure, dependency issue, unclear API usage, implementation blocker, or tool-capability need calls for GitHub solutions. Not for source or remote-system changes.