trellis-brainstormlisted

# Brainstorm - Requirements Discovery (AI Coding Enhanced) **CoreRule**: 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. For each question, provide your recommended answer. Ask the questions one at a time. If a question can be answered by exploring the codebase, explore the codebase instead. --- Guide AI through collaborative requirements discovery **before implementation**, optimized for AI coding workflows: * **Task-first** (capture ideas immediately) * **Action-before-asking** (reduce low-value questions) * **Research-first** for technical choices (avoid asking users to invent options) * **Diverge → Converge** (expand thinking, then lock MVP) --- ## When to Use Triggered from /trellis:start when the user describes a development task, especially when: * requirements are unclear or evolving * there are multiple valid implementation paths * trade-offs matter (UX, reliability, maintainability, cost, performance) * the user might not know the best options up front --- ## Core Principles (Non-negotiable) 1. **Task-first (capture early)** Always ensure a task exists at the start so the user's ideas are recorded immediately. 2. **Action before asking** If you can derive the answer from repo code, docs, configs, conventions, or quick research — do that first. 3. **One question per message** Never overwhelm the user w