| name | brainstorming |
| description | Use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Use when user asks to design, plan, or think through a feature before implementing. Explores intent, requirements, and design through collaborative dialogue.
|
| version | 1.0.0 |
| user-invocable | true |
| argument-hint | descrivi cosa vuoi creare o progettare |
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.
Design 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.
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
Examples
Example 1: Simple Component Design
User: "Create a button component"
Process: Ask about variants (primary/secondary), sizes, states (hover/disabled), accessibility needs
Design: Present component API, styling approach, test strategy
Output: Design doc saved, ready for implementation
Example 2: Feature Design
User: "Add user authentication"
Process: Ask about auth method (OAuth/credentials), scope (login only or full session), integrations needed
Design: Present architecture, data flow, security considerations, testing approach
Output: Design doc saved, ready for implementation
Example 3: Refactoring Design
User: "Reorganize the component folder structure"
Process: Ask about current pain points, desired organization, migration strategy
Design: Present new structure, migration plan, impact analysis
Output: Design doc saved, ready for implementation
Troubleshooting
Issue: User says "just build it, I'll figure it out as we go"
Solution: Explain that design prevents rework. Even 5 minutes of design saves 30+ minutes of rework. Present a quick design anyway.
Issue: Design seems too simple to need documentation
Solution: Document it anyway. Simple designs are where assumptions cause the most wasted work. Keep it brief (few sentences) but write it.
Issue: User approves design but wants changes during implementation
Solution: This is expected. Go back to brainstorming, revise design, get new approval, then implement revised design.
