brainstorming-ideaslisted

# Brainstorming Ideas Turn a vague idea or draft plan into a well-formed design before coding. Keep the session collaborative, question-driven, and small enough to change direction. ## Core rules - Ask one question at a time. - Use an interactive question tool when available; do not emulate menus in plain text. - Inspect code before asking when code can answer. - Offer 2-3 options with trade-offs and mark one recommendation. - Always allow a free-text or Other answer when options may not fit. - Cut speculative features and route task breakdown to `spec-plan`. ## Interactive questions When a runtime question tool is available, use it for every choice point: - single-select for one path, approach, or confirmation - multi-select for multiple goals, risks, constraints, or audiences - free text for problem statements, plan details, or custom answers - options plus Other when you can suggest likely answers but need flexibility Do not ask the user to type `1`, `2`, or `3` unless no interactive tool is available. If no tool exists, use concise labeled options and include `Other`. ## Load domain context Before design questions, look for relevant project docs: - `CONTEXT.md` - `CONTEXT-MAP.md` - `docs/adr/` - nearest `*/CONTEXT.md` or `*/docs/adr/` Read them when present. Use those terms in questions and designs. If no docs exist, create them only with user approval and only when a real term or decision is resolved. ## Understand the idea If the user did not supply a topic