brainstorming

# Execute → New feature, product behavior, UI/component design, architecture/contract change, or ambiguous medium/high-complexity work? → **Design first. No implementation until the needed design/spec is approved.** 1. Explore project context → read authority docs, check for existing patterns 2. Ask clarifying questions one at a time (prefer multiple choice) 3. Propose 2-3 approaches with trade-offs and your recommendation 4. Present design sections → get user approval after each 5. Write spec → self-review → user review → transition to writing-plans → HARD GATE: For tasks that match this skill, do NOT write code, scaffold projects, or invoke implementation skills until design/spec approval is satisfied. # Brainstorming Ideas Into Designs Help turn ideas into fully formed designs and specs through natural collaborative dialogue. Start by understanding the current project context and authority boundary, then ask questions one at a time to refine the idea. Once you understand what you're building, present the smallest design artifact that stabilizes the work and get the required approval. <HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take implementation action for work that matches this skill until you have presented the required design/spec and the user has approved it where this workflow requires approval. </HARD-GATE> ## Route Away When It Is Small Do not force this workflow onto low-complexity work. A tiny word...