analyze

# /supergraph:analyze Analyze first, implement never. No code until approach is approved. Announce: "🔍 /supergraph:analyze — framing problem, checking graph risk..." ## When - Ambiguous requirements - Multiple valid approaches - Task spans modules - Graph shows high blast-risk (hub/bridge nodes) - User says "how should I..." or "what's the best way..." Skip for: typo fixes, config changes, clear mechanical edits. ## Workflow **0. Read CONTEXT.md (if exists):** ```bash cat CONTEXT.md 2>/dev/null | head -60 ``` Use existing domain vocabulary in all analysis — never invent new terms for concepts already named. **1. Frame the problem:** - Goal: [one sentence] - Known constraints - Open questions **1b. Score ambiguity (before grilling):** | Signal | +1 if... | |---|---| | Ambiguous scope | touches multiple modules without naming one | | No explicit path | no file/package/feature named | | Multiple intents | could be bug fix, feature, refactor, or question | | First interaction | no established context this session | | Score | Action | |---|---| | 0–1 | Skip grilling — proceed with best available info | | 2 | Show 1-line routing summary, wait for confirm | | 3–4 | Grill: ask focused questions with recommended options | **Auto-skip grilling entirely if:** user said "go"/"just do it", trivial fix (<15 lines, 1 file), explicit mode command, or active plan already exists. **Grilling rules:** ONE question at a time, offer recommended answer, max 3 questions. Stop when goal...