brainstorming-design-docs

# Brainstorming to Design Doc This skill runs a structured dialogue that takes a raw idea and builds it into a complete design document through collaborative, incremental development. Every section gets user approval before moving forward — no surprises at the end. > **Scope:** Produces prose and Markdown only. Does not write code, scripts, or formulas. --- ## Core Principles **Ask one question at a time.** Asking multiple questions at once creates cognitive load and produces vague answers. Work through clarifications sequentially — each answer shapes the next question. **Prefer multiple choice.** When asking clarifying questions, offer 2–4 options where possible. "Which of these best describes your goal: (a) reduce manual work, (b) improve visibility for stakeholders, or (c) standardize how teams do X?" gets a better answer than "what is your goal?" **Propose alternatives before committing.** Never design toward a single solution from the start. Generate two or three distinct approaches, present their trade-offs, and recommend one — then get buy-in before building out the detail. **Cut scope ruthlessly.** Only include what the idea actually needs right now. If a feature, section, or requirement sounds like "it would also be nice to..." it belongs in an open questions section, not in the design. **Validate incrementally.** Present the design one section at a time and confirm each before moving to the next. A surprise at section six wastes the work of sections two thr...