investigate

# /investigate Read-only fact-gathering — understand the codebase before acting. > **Structured execution spec:** [`protocol.yon`](protocol.yon). Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the `@STAMP` date. > **Caller Options.** Before executing, run the Caller Options protocol (`caller-options/SKILL.md`): triage this invocation for material optionality across the venues and modes declared in front-matter; if one path clearly dominates, proceed silently; otherwise surface the options to the caller. A resolved-invocation marker means COP already ran — execute the fixed combination directly, do not re-enter COP. > **Fact-Gathering Protocol. READ ONLY.** No plans, no code, no refactors. Just facts. ## Phase 1 — Context Loading 1. **Parse the query** — identify target files, directories, or concepts from the user's request. 2. **List files** — read the target directory structure. 3. **Read entrypoints** — load `package.json`, `README.md`, index files, or whatever serves as the front door to the target area. ## Phase 2 — Pattern Discovery 1. **Search for usages** — grep for functions, components, or patterns relevant to the query. Follow call sites and import chains. 2. **Load relevant skills** — check if a domain skill applies: - If your repository maintains its own standards skills (UI conventions, coding standards), load the matching one — this pack does not s...