plastic-intent-researching

# Research Investigate a topic related to the active intent. Choose the right depth, produce a cited report. **Announce at start:** "I'm researching [topic] for intent {id} — {name}." ## Active Intent Gate Before proceeding, resolve the active intent: 1. **Detect store:** Read `~/.plastic/projects.yml`, match CWD against registered project paths. If match → project store at `~/.plastic/projects/{slug}/store/`. If no match → global store at `~/.plastic/store/`. 2. **Find active intent:** Read `INDEX.md` from the detected store. Look under `## Active`. If exactly one → use it. If multiple → ask which. If none → refuse: "No active intent. Create one first with /plastic-intent-creating" 3. **Resolve intent directory:** `{store}/store/{id}--{slug}/` ## Check Prior Work First QMD-first (when available): before scanning the store with grep/Read or searching the web, run `ruby ~/.plastic/scripts/qmd-sync search "<terms>"` to surface candidate, prior, or related intents and existing research, then open the authoritative intent file for any hit you act on. Reusing a prior report beats re-deriving it. The command is a no-op when QMD is absent, so fall back to the existing INDEX.md / file scan. ## Depth Decision Before starting research, assess the question against these criteria: ### Shallow Research Use when: - The question is narrow and factual (e.g., "what's the API for X?", "does library Y support Z?") - A single source or quick search is sufficient - The answer is likely ...