interviewlisted

# /interview — Elicit Knowledge Through Dialogue Interview the user to draw out knowledge that lives in their head (and in their artifacts), then stage it as structured markdown in the `intake/` tree. Unlike `/extract` (reads the current conversation) or `/intake` (captures/scans external sources — URLs, snippets, files), `/interview` *asks questions* — the answers become the knowledge. Output is staged for **manual review** (the `/meeting-notes` model), never auto-promoted. ## Step 0: Resolve Config Read `~/.gemini/antigravity/aria-knowledge.local.md` and extract `knowledge_folder`. If the file doesn't exist, stop: "aria-knowledge is not configured. Run /setup to get started." ## Step 1: Resolve Mode, Topic, Grounding Parse arguments: first positional = **mode** (`project` | `knowledge` | `deep-dive`). Remaining text = **topic**. `--ground=<path|glob|url>[,...]` = optional grounding artifacts. If no mode given, ask: "Which interview — `project` (scope a new build), `knowledge` (get a topic into the KB), or `deep-dive` (extract rationale behind something you already built)?" **Derive the slug** from the topic (kebab-case, ≤6 words). If no topic yet, ask for a one-line subject. ### GATE — deep-dive requires a basis (explicit early-return) **If mode is `deep-dive` AND no `--ground` was provided AND no basis is named in the topic:** > STOP. Do not ask any interview questions. Emit: > > "`deep-dive` extracts the rationale behind something that already exists, so it need