brainstorminglisted

# Brainstorming ## Overview Refine a design collaboratively before any code or plan exists. Walk through the design one section at a time, always leading with a concrete recommendation, and validate each section with the partner before moving on. The goal is a design the partner fully understands and can defend, not a design handed to them fully formed. **Announce at start:** "I'm using the brainstorming skill to work through this design with you." ## Core Rules These are the heart of the skill, follow them on every turn: 1. **Every question MUST include a recommendation.** Lead with "I'd lean toward X because Y. Does that match your thinking?", never an open-ended "what do you think?". The partner is validating or redirecting a proposal, not staring at a blank page. This is what keeps momentum and teaches the reasoning as you go. 2. **One question at a time.** Don't overwhelm. Ask, wait, incorporate the answer, then ask the next. This means one question *per turn*, not one decision question with a second "and also…" tacked on the end. If you need context before you can recommend, that context question IS the turn: ask it alone and wait. Resist the pull to gather background and validate a decision in the same message; splitting them is what keeps the partner in control and each answer unambiguous. 3. **Multiple choice preferred** where it fits. Offer A / B / C options, each with its trade-off named, so the choice is concrete and the partner