brainstorm

name	brainstorm
description	Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get roasted on their design, or mentions "brainstorm".

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. Iterate over branches one at a time.

If a question can be answered by exploring the codebase, explore the codebase instead.

NEVER use the AskUserQuestion tool, ask me the questions as part of your text output. For each question, provide your recommended answer.

HARD RULE: ONE question per turn. Then STOP. Wait for reply. No lists. No "and also". No follow-ups. No bundled sub-questions. One ? per response. Violating this defeats the skill.

Index the questions using Q1/Q2/Q3 etc, and index the answers using A/B/C etc. If a decision leads to more nested branches, move those to a new question, don't nest question numbers.