brainstorm-gatelisted

# Brainstorm Gate — Design Before Code When a task is ambiguous or has multiple valid approaches, brainstorm the design with the user BEFORE writing any code. No implementation until the design is approved. ## When This Activates - User describes a feature without specifying the approach - Multiple valid architectures exist (and choosing wrong is expensive) - The task touches 3+ files or introduces a new pattern - You find yourself making assumptions about behavior - The phrase "it depends" applies to the implementation ## When to Skip - Bug fix with a clear root cause - User gave explicit, unambiguous instructions - Mechanical task (rename, move, update config) - Single-file change with obvious implementation ## Protocol ### 1. Clarify the Problem Before proposing solutions, confirm you understand: - **What** the user wants (observable behavior, not implementation) - **Why** they want it (the motivation shapes the solution) - **Constraints** (performance, compatibility, timeline, existing patterns) Ask at most 2-3 focused questions. Don't interrogate. ### 2. Propose Options Present 2-3 approaches, each with: - **One-line summary** of the approach - **Pros**: why you'd choose this - **Cons**: what you'd give up - **Effort**: relative complexity (low / medium / high) Lead with your recommendation and say why. ### 3. Wait for Approval Do NOT proceed to implementation until the user explicitly picks an approach or says "go ahead." Silence or ambiguity means "wait."