brainstorming

# Universal Brainstorming Protocol ## Purpose Bridge the gap between a vague user intent ("Make it pop", "I need a referral system") and a concrete, actionable plan. This skill doesn't just *clarify* requirements — it actively **generates ideas**, helps the user **evaluate trade-offs**, and converges on a **confirmed design** before any code is written. ## Red Flags (Anti-Rationalization) **STOP and READ THIS if you are thinking:** - "I'll just start coding, the requirements are clear enough" → **WRONG**. Even "clear" tasks have hidden assumptions. Validate first — rework costs 3x more than upfront clarification. - "I'll skip idea generation and go straight to the obvious solution" → **WRONG**. The obvious solution is often the first one, not the best one. Generate at least 3 options for MEDIUM/COMPLEX tasks. - "The user didn't ask for alternatives, so I'll just propose one" → **WRONG**. Brainstorming means expanding the solution space. Always present options with trade-offs. - "I can't visualize this without a whiteboard" → **WRONG**. Use Mermaid, ASCII, or structured bullet lists — text-based visualization is always possible. - "The user ignored my question, I'll guess" → **WRONG**. Don't guess on ambiguous requirements. Restate why the answer matters: *"To avoid breaking X, I need to know Y."* - "This is too simple for a full brainstorm" → **OK, but state it explicitly**: *"This is trivial — I propose X. Proceed?"* Never silently skip the process. ## Capabilities - C...