brainstormlisted

# Brainstorm Sharpen a vague idea into a confirmed proposal through one-question-at-a-time dialogue. The cheapest moment to find ambiguity is before any plan, spec, or code exists — once building starts, switching costs lock in the wrong thing. ## When to use - The ask is underspecified — missing who, why, what success looks like, or the binding constraint. - New feature, project, or "refine this idea" / "stress-test my thinking." - User says "brainstorm", "grill me", "interview me", "refine this idea", "头脑风暴", "帮我打磨想法", or "盘问我". - You're tempted to silently fill ambiguous requirements before a spec exists. **Not for:** unambiguous asks ("rename this variable"), pure info requests, or when the user has explicitly asked for speed over verification. ## Steps 1. **Hypothesize with a confidence number.** If in a codebase, explore project context first (Glob/Grep/Read for architecture, patterns, constraints) before forming the hypothesis. Before asking anything, write your best read of what the user wants in one sentence, plus an honest confidence (0–100%): ``` HYPOTHESIS: You want a way to answer "how are we doing?" in standup, and "dashboard" was the convention that came to mind. CONFIDENCE: ~30% — missing: who it's for, what "metrics" means, what success looks like ``` Below ~70%, append what's still unresolved. The number forces honesty — if you can't predict the user's reaction to the next three questions, the number is wrong. 2. **Ask ONE q