unioss-brainstorminglisted

# Brainstorming Ideas Into Designs Help turn ideas into fully formed designs and specs through natural collaborative dialogue. Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval. <HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity. </HARD-GATE> ## Pipeline mode vs. standalone **In the gated pipeline** the orchestrator invokes you at GATE 0 to work the investigation's Open Questions, and nothing more. Steps 5–9 of the checklist below belong to the pipeline, not to you: the design presentation is Decision prompt **(c)** at Flow step 3c, the spec is written by the `unioss-spec` agent, and the plan comes from `unioss-planner` at GATE 2. Append your answers to `## Clarifications`, return, and stop — do not present a design, write `spec.md`, or invoke `unioss-writing-plans`. **Standalone** (no round path), run the whole checklist as written. ## Anti-Pattern: "This Is Too Simple To Need A Design" Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple pr