kwbrainstormlisted

<brain_dump> #$ARGUMENTS </brain_dump> # Brainstorm Get everything out of your head and into one place. Pull in references. Find the shape of the problem before you commit to a plan. ## When to Use * After a meeting where next steps need to be figured out * Starting a new project, campaign, or strategy * "I need to think through X", "Let me brain dump", "Help me figure this out" * When you have scattered inputs (notes, docs, transcripts) that need organizing ## Process ### Step 1: Capture the brain dump Accept whatever the user gives you. This might be: * A pasted meeting transcript * A voice-to-text dump * Bullet points and half-formed thoughts * A link to a document * "Here's what I'm thinking about..." **Do not organize yet.** Just acknowledge what you received and identify what type of input it is. If the user hasn't given you anything yet, prompt: > "What are you working on? You can paste meeting notes, describe the problem, or just start talking. I'll help organize it." ### Step 2: Extract the core elements From the brain dump, pull out: * **Key decisions** that need to be made * **Open questions** that don't have answers yet * **Constraints** (timeline, budget, dependencies, blockers) * **Stakeholders** and what they care about * **Data points** mentioned (numbers, metrics, references) * **Ideas and options** that were floated (even half-baked ones) Present these back as a structured summary: ``` ## What I Heard **The problem:** [One senten