brainstormlisted

# Brainstorm Use this skill to turn a rough idea into a concrete direction before implementation. ## When to Use This Skill Use this skill when the user: - Asks to brainstorm, explore, or think through an idea - Wants help shaping a feature before coding - Needs options, tradeoffs, or a recommendation - Is unsure about scope, UX, architecture, or workflow - Wants a spec or plan before implementation Do not use this skill when the request is already specific and the user clearly wants code changes now. ## Core Rules - Do not start implementing while still in brainstorming mode - Ask one clarifying question at a time when requirements are fuzzy - Prefer concrete choices over vague discussion - Propose 2-3 approaches with tradeoffs and a recommendation - Keep the design proportional to the task; simple ideas only need a short design - Follow the existing codebase and product patterns when brainstorming changes to an existing project ## Workflow ### 1. Understand Context First Before proposing solutions: - Inspect the relevant code, docs, or task context - Identify constraints from the existing system - Notice whether the request is actually multiple problems that should be split apart If the idea is too broad for one pass, say so and help the user split it into smaller parts. ### 2. Clarify the Goal Ask focused questions to understand: 1. What problem this solves 2. Who it is for 3. What constraints matter 4. What success looks like Prefer multiple-choice questio