brainstorminglisted

# Turning Ideas into Designs Develop an idea into a complete design and specification through natural collaborative conversation. First understand the current project context, then refine the idea by asking one question at a time. Once you understand what to build, present the design and obtain user approval. #### Prohibition Rules Do not call implementation skills. Do not write code. Do not run project scaffolding. Do not take implementation actions. Hold off until you present the design and the user approves it. Apply this to every project, no matter how simple it looks. ## Contents - [Anti-pattern: "Too simple to need a design"](#anti-pattern-too-simple-to-need-a-design) - [Checklist](#checklist) - [Process Flow](#process-flow) - [Process](#process) - [After the Design](#after-the-design) - [Core Principles](#core-principles) - [Visual Companion](#visual-companion) ## Anti-pattern: "Too simple to need a design" Every project goes through this procedure. To-do lists, single-function utilities, configuration changes, all of them. In "simple" projects, unexamined assumptions cause the most wasted work. A design can be short (a few sentences for a truly simple project), but you must present it and obtain approval. ## Checklist Create a task for each item below and complete them in order: 1. Explore the project context. Review files, documents, and recent commits. 2. Present the visual companion (when visual questions are expected). A standalone message, not merged w