Brainstorming Ideas Into Designs
When to Use
Use this skill before:
- building a new feature
- changing behavior in a meaningful way
- creating a new component or workflow
- turning a rough idea into an implementation-ready design
Usage
Use a short design discussion when consequential choices remain open.
If the user has already supplied a workable design and asked for implementation,
record the essential assumptions and proceed with the authorized work.
For small, reversible changes, a concise inline design is enough.
inspect current context
-> identify decisions that affect the outcome
-> resolve consequential gaps
-> state the chosen approach and acceptance checks
-> implement when authorized
Decision Boundaries
Ask for input when the answer changes the product goal, user experience,
public contract, data retention, or an irreversible action.
Use existing project patterns for routine implementation choices.
Continue independent research and preparation while a necessary answer is pending.
An explicit brainstorming-only request remains a discussion task.
Practical Design Checklist
- Read the relevant code, requirements, and previous decisions.
- State the problem, intended user, and observable success criteria.
- Identify only the uncertainties that materially affect the solution.
- Compare alternatives when there is a real tradeoff; do not manufacture options.
- Choose a small, coherent implementation and explain its main tradeoff.
- Record an enduring design document only when future work needs it.
- Continue into implementation if the user requested execution.
Example
Request: Add CSV export to the existing table.
Known: Current filters and columns define the exported data.
Decision: Reuse the existing authorized data-fetch path.
Check: Export filtered rows, escape CSV cells, preserve column order.
Clarify only if export scope or access requirements remain ambiguous.
Handoff
Use a written plan when dependencies or scope need one.
Do not require a second plan or approval merely to invoke another skill.
Keep original user constraints and acceptance checks with the handoff.
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
- Ask concise questions only for unresolved material choices; group closely related gaps when useful
- 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
- Invite corrections without blocking already authorized implementation
- 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:
- For substantial designs, save the durable decisions to
docs/plans/YYYY-MM-DD-<topic>-design.md
- Use elements-of-style:writing-clearly-and-concisely skill if available
- Include the design with the task changes when a commit is requested
Implementation:
- Continue the requested implementation once consequential decisions are resolved
- Use writing-plans when the task needs an enduring plan; avoid forced skill chains
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 - Remove unnecessary features from designs
- Explore alternatives - Compare alternatives when they expose a real tradeoff
- Incremental validation - Confirm unresolved consequential choices; reuse existing authorization
- Be flexible - Go back and clarify when something doesn't make sense
1---
2name: brainstorming
3description: 'Use before creative product or engineering work when the user wants to design a feature, component, workflow, behavior change, or other solution whose goals, constraints, and tradeoffs need exploration before implementation.'
4zh_description: "用于在实现前澄清创意型产品或工程需求,探索目标、约束、方案与取舍。"
5version: "1.0.2"
6author: "seaworld008"
7source: "in-house"
8source_url: ""
9tags: '["brainstorming", "planning", "workflow"]'
10created_at: "2026-03-04"
11updated_at: "2026-09-06"
12quality: 3
13complexity: "intermediate"
14metadata:
15 source: https://skillmd.com/skills/seaworld008/brainstorming
16---
17
18# Brainstorming Ideas Into Designs
19
20## When to Use
21
22Use this skill before:
23
24- building a new feature
25- changing behavior in a meaningful way
26- creating a new component or workflow
27- turning a rough idea into an implementation-ready design
28
29## Usage
30
31Use a short design discussion when consequential choices remain open.
32If the user has already supplied a workable design and asked for implementation,
33record the essential assumptions and proceed with the authorized work.
34For small, reversible changes, a concise inline design is enough.
35
36```text
37inspect current context
38-> identify decisions that affect the outcome
39-> resolve consequential gaps
40-> state the chosen approach and acceptance checks
41-> implement when authorized
42```
43
44## Decision Boundaries
45
46Ask for input when the answer changes the product goal, user experience,
47public contract, data retention, or an irreversible action.
48Use existing project patterns for routine implementation choices.
49Continue independent research and preparation while a necessary answer is pending.
50An explicit brainstorming-only request remains a discussion task.
51
52## Practical Design Checklist
53
541. Read the relevant code, requirements, and previous decisions.
552. State the problem, intended user, and observable success criteria.
563. Identify only the uncertainties that materially affect the solution.
574. Compare alternatives when there is a real tradeoff; do not manufacture options.
585. Choose a small, coherent implementation and explain its main tradeoff.
596. Record an enduring design document only when future work needs it.
607. Continue into implementation if the user requested execution.
61
62## Example
63
64```text
65Request: Add CSV export to the existing table.
66Known: Current filters and columns define the exported data.
67Decision: Reuse the existing authorized data-fetch path.
68Check: Export filtered rows, escape CSV cells, preserve column order.
69Clarify only if export scope or access requirements remain ambiguous.
70```
71
72## Handoff
73
74Use a written plan when dependencies or scope need one.
75Do not require a second plan or approval merely to invoke another skill.
76Keep original user constraints and acceptance checks with the handoff.
77
78## The Process
79
80**Understanding the idea:**
81- Check out the current project state first (files, docs, recent commits)
82- Ask questions one at a time to refine the idea
83- Prefer multiple choice questions when possible, but open-ended is fine too
84- Ask concise questions only for unresolved material choices; group closely related gaps when useful
85- Focus on understanding: purpose, constraints, success criteria
86
87**Exploring approaches:**
88- Propose 2-3 different approaches with trade-offs
89- Present options conversationally with your recommendation and reasoning
90- Lead with your recommended option and explain why
91
92**Presenting the design:**
93- Once you believe you understand what you're building, present the design
94- Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced
95- Invite corrections without blocking already authorized implementation
96- Cover: architecture, components, data flow, error handling, testing
97- Be ready to go back and clarify if something doesn't make sense
98
99## After the Design
100
101**Documentation:**
102- For substantial designs, save the durable decisions to `docs/plans/YYYY-MM-DD-<topic>-design.md`
103- Use elements-of-style:writing-clearly-and-concisely skill if available
104- Include the design with the task changes when a commit is requested
105
106**Implementation:**
107- Continue the requested implementation once consequential decisions are resolved
108- Use writing-plans when the task needs an enduring plan; avoid forced skill chains
109
110## Key Principles
111
112- **One question at a time** - Don't overwhelm with multiple questions
113- **Multiple choice preferred** - Easier to answer than open-ended when possible
114- **YAGNI** - Remove unnecessary features from designs
115- **Explore alternatives** - Compare alternatives when they expose a real tradeoff
116- **Incremental validation** - Confirm unresolved consequential choices; reuse existing authorization
117- **Be flexible** - Go back and clarify when something doesn't make sense