brainstorminglisted

# Brainstorming Ideas Into Designs ## Overview 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> - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## 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 projects), but you MUST present it and get approval. ## Anti-Patterns - Delegating or evaluating without a scoped success condition: The output becomes hard to review and easy to overbuild. - Skipping the evidence step: A workflow that cannot be re-checked quickly is not ready for handoff. - Bundling unrelated subtasks together: It creates noisy prompts, weaker ownership, and avoidable integration risk. ## Verification Protocol Before claiming "skill applied successfully": 1. Pass/fail: The Brain