brainstorming

name	brainstorming
description	MANDATORY skill for ANY creative or exploratory work. When invoked, STRICTLY follow the step-by-step process: understand context, ask questions one at a time, explore approaches, present solution incrementally. Applies to software design, content creation, problem-solving, planning, or any ideation task.

Brainstorming: Collaborative Ideation Process

Overview

Transform any idea into a fully formed solution through structured collaborative dialogue.

CRITICAL: When this skill is invoked, you MUST follow the process below step-by-step. Do NOT skip directly to providing answers.

The Process (MANDATORY STEPS)

Step 1: Understanding Context

• Check relevant context first (files, docs, recent work, existing materials)
• Identify what domain/area this request belongs to
• Note any constraints or existing patterns

Step 2: Understanding the Idea

• 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: What is the goal? Why does this matter?
  • Constraints: What limitations exist? (time, resources, technical, etc.)
  • Success criteria: What does "good" look like?
  • Audience/Users: Who is this for?

Step 3: Exploring Approaches

• Once you understand the need, propose 2-3 different approaches with trade-offs
• Present options conversationally with your recommendation and reasoning
• Lead with your recommended option and explain why
• Highlight pros/cons of each approach
• Ask which direction resonates

Step 4: Presenting the Solution

• Once direction is chosen, present the solution/design
• Break it into sections of 200-300 words
• Ask after each section whether it looks right so far
• Cover relevant aspects based on domain:
  • Software: architecture, components, data flow, error handling, testing
  • Content: structure, key points, tone, format
  • Planning: phases, milestones, dependencies, risks
  • Problem-solving: root causes, solution steps, validation
• Be ready to go back and clarify if something doesn't make sense

Step 5: Finalization

• Once all sections are validated, ask if user wants documentation
• If yes, write to @archive/YYYY-MM-DD-<topic>.md
• After saving, open the file:
  • macOS: Prefer Typora (open -a Typora [file]), fallback to default (open [file])
  • Linux: Use xdg-open [file]

Key Principles (NON-NEGOTIABLE)

• 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 complexity from all solutions
• Explore alternatives - Always propose 2-3 approaches before settling
• Incremental validation - Present solution in sections, validate each
• Be flexible - Go back and clarify when something doesn't make sense
• No shortcuts - Even if the request seems simple, follow the process

Examples of When This Applies

• Software design (features, components, architecture)
• Content creation (articles, documentation, presentations)
• Problem-solving (debugging strategies, process improvements)
• Planning (project plans, learning paths, workflows)
• Creative work (naming, branding, user experience)
• Decision-making (evaluating options, trade-off analysis)
• Question generation (interview questions, survey design, discussion prompts)