issuelisted

GitHub issue. Two-phase: socratic gate sharpens intent (§1); investigate codebase ∧ file issue downstream (§2-§8). ## Process 1. **Socratic gate** (always-on, ⊥ skip flag, ⊥ `--quick` bypass): - ⊥ $ARGUMENTS → ask user for issue intent (problem, idea, bug, feature) before gate runs. - Invoke `core:socratic` skill w/ $ARGUMENTS. Gate runs single-Q loop until convergence triple satisfied: 1. explicit goal — observable symptom (bug) ∨ concrete behavior delta (feature/refactor) 2. acceptance criterion ∨ repro step — one verifiable outcome ∨ reproducible failure 3. §V/§T citation ∨ ⊥-spec flag — cite invariant/task this concerns, ∨ flag explicitly out-of-spec - Concrete first-turn input passes ≤ 1 turn; vague → dialogue continues until convergence. Per skill spec: ≥ 3 turns w/o convergence → escape protocol offered. - Escape protocol ("just file it" ∨ "skip questions" ∨ "I know what I want"): stops dialogue but ⊥ bypasses gate — unmet criteria become explicit `## Unresolved` callouts in §5 issue body. Gaps stay visible to team. - Rationale: GitHub issues = team-shared artifacts; validity bar > author keystroke savings. 2. **Investigate codebase:** - Search relevant files via Grep / Glob - Read related code → understand current implementation - Check git log for recent changes in affected areas - Identify affected components / modules 3. **Gather details:** - Type: bug, feature, enhancement, refactor - Affected files ∧ code paths