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.
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.
Checklist
You MUST create a task for each of these items and complete them in order:
- Explore project context — check files, docs, recent commits
- Ask clarifying questions — one at a time, understand purpose/constraints/success criteria
- Propose 2-3 approaches — with trade-offs and your recommendation
- Present design — in sections scaled to their complexity, get user approval after each section
- Write design doc — save to
docs/plans/YYYY-MM-DD-<topic>-design.md and commit
- Transition to implementation — invoke writing-plans skill to create implementation plan
Process Flow
digraph brainstorming {
"Explore project context" [shape=box];
"Ask clarifying questions" [shape=box];
"Propose 2-3 approaches" [shape=box];
"Present design sections" [shape=box];
"User approves design?" [shape=diamond];
"Write design doc" [shape=box];
"Invoke writing-plans skill" [shape=doublecircle];
"Explore project context" -> "Ask clarifying questions";
"Ask clarifying questions" -> "Propose 2-3 approaches";
"Propose 2-3 approaches" -> "Present design sections";
"Present design sections" -> "User approves design?";
"User approves design?" -> "Present design sections" [label="no, revise"];
"User approves design?" -> "Write design doc" [label="yes"];
"Write design doc" -> "Invoke writing-plans skill";
}
The terminal state is invoking writing-plans. Do NOT invoke frontend-design, mcp-builder, or any other implementation skill. The ONLY skill you invoke after brainstorming is writing-plans.
The Process
Understanding the idea:
- Check out the current project state first (files, docs, recent commits)
- Ask questions one at a time to refine the idea
- Prefer multiple choice questions when possible, but open-ended is fine too
- Only one question per message - if a topic needs more exploration, break it into multiple questions
- Focus on understanding: purpose, constraints, success criteria
Exploring approaches:
- Propose 2-3 different approaches with trade-offs
- Present options conversationally with your recommendation and reasoning
- Lead with your recommended option and explain why
Presenting the design:
- Once you believe you understand what you're building, present the design
- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced
- Ask after each section whether it looks right so far
- Cover: architecture, components, data flow, error handling, testing
- Be ready to go back and clarify if something doesn't make sense
After the Design
Documentation:
- Write the validated design to
docs/plans/YYYY-MM-DD-<topic>-design.md
- Use elements-of-style:writing-clearly-and-concisely skill if available
- Commit the design document to git
Implementation:
- Invoke the writing-plans skill to create a detailed implementation plan
- Do NOT invoke any other skill. writing-plans is the next step.
Key Principles
- One question at a time - Don't overwhelm with multiple questions
- Multiple choice preferred - Easier to answer than open-ended when possible
- YAGNI ruthlessly - Remove unnecessary features from all designs
- Explore alternatives - Always propose 2-3 approaches before settling
- Incremental validation - Present design, get approval before moving on
- Be flexible - Go back and clarify when something doesn't make sense
1---2name: brainstorming3description: "Use when starting creative work (features, components, functionality, or behavior changes) to clarify user intent, requirements, and design before implementation."4metadata:5 source: https://skillmd.com/skills/thedaviddias/brainstorming6---78# Brainstorming Ideas Into Designs910## Overview1112Help turn ideas into fully formed designs and specs through natural collaborative dialogue.1314Start 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.1516<HARD-GATE>17Do 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.18</HARD-GATE>1920## Anti-Pattern: "This Is Too Simple To Need A Design"2122Every 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.2324## Checklist2526You MUST create a task for each of these items and complete them in order:27281. **Explore project context** — check files, docs, recent commits292. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria303. **Propose 2-3 approaches** — with trade-offs and your recommendation314. **Present design** — in sections scaled to their complexity, get user approval after each section325. **Write design doc** — save to `docs/plans/YYYY-MM-DD-<topic>-design.md` and commit336. **Transition to implementation** — invoke writing-plans skill to create implementation plan3435## Process Flow3637```dot38digraph brainstorming {39 "Explore project context" [shape=box];40 "Ask clarifying questions" [shape=box];41 "Propose 2-3 approaches" [shape=box];42 "Present design sections" [shape=box];43 "User approves design?" [shape=diamond];44 "Write design doc" [shape=box];45 "Invoke writing-plans skill" [shape=doublecircle];4647 "Explore project context" -> "Ask clarifying questions";48 "Ask clarifying questions" -> "Propose 2-3 approaches";49 "Propose 2-3 approaches" -> "Present design sections";50 "Present design sections" -> "User approves design?";51 "User approves design?" -> "Present design sections" [label="no, revise"];52 "User approves design?" -> "Write design doc" [label="yes"];53 "Write design doc" -> "Invoke writing-plans skill";54}55```5657**The terminal state is invoking writing-plans.** Do NOT invoke frontend-design, mcp-builder, or any other implementation skill. The ONLY skill you invoke after brainstorming is writing-plans.5859## The Process6061**Understanding the idea:**62- Check out the current project state first (files, docs, recent commits)63- Ask questions one at a time to refine the idea64- Prefer multiple choice questions when possible, but open-ended is fine too65- Only one question per message - if a topic needs more exploration, break it into multiple questions66- Focus on understanding: purpose, constraints, success criteria6768**Exploring approaches:**69- Propose 2-3 different approaches with trade-offs70- Present options conversationally with your recommendation and reasoning71- Lead with your recommended option and explain why7273**Presenting the design:**74- Once you believe you understand what you're building, present the design75- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced76- Ask after each section whether it looks right so far77- Cover: architecture, components, data flow, error handling, testing78- Be ready to go back and clarify if something doesn't make sense7980## After the Design8182**Documentation:**83- Write the validated design to `docs/plans/YYYY-MM-DD-<topic>-design.md`84- Use elements-of-style:writing-clearly-and-concisely skill if available85- Commit the design document to git8687**Implementation:**88- Invoke the writing-plans skill to create a detailed implementation plan89- Do NOT invoke any other skill. writing-plans is the next step.9091## Key Principles9293- **One question at a time** - Don't overwhelm with multiple questions94- **Multiple choice preferred** - Easier to answer than open-ended when possible95- **YAGNI ruthlessly** - Remove unnecessary features from all designs96- **Explore alternatives** - Always propose 2-3 approaches before settling97- **Incremental validation** - Present design, get approval before moving on98- **Be flexible** - Go back and clarify when something doesn't make sense