brainstorm

# Brainstorm $ARGUMENTS The conversation that happens *before* an artifact exists. Every other planning skill here produces something — a PRD, a plan, issues, a design. This one is allowed to produce nothing, and that is its point. ## The zero option is a real candidate Price "build nothing" against the proposal properly. Not as a strawman, not as a sentence acknowledged and moved past — as a genuine option with its own costs: - what breaks or stays broken if nobody does this - who currently absorbs that, and how much it costs them - how long the problem has existed without being fixed, and what that says about it - what the codebase carries forever once this exists: another surface, another migration path, another thing that has to keep working If the zero option wins, say so and stop. **Do not invent a deliverable to justify the conversation.** A brainstorm that ends in "this is not worth building, and here is what it would have cost" has done its job. ## Steps ### Step 1: Understand before proposing Explore the actual codebase before shaping anything. Read what exists, grep for prior attempts, check whether the problem is already solved somewhere. Ask what the user is trying to achieve, not what they want built. The stated request is a proposed solution; the problem behind it is what matters. Keep asking until you can state the problem without naming the solution. ### Step 2: Shape the options Produce at least three genuinely different approaches, one of whic...