Ultimate Brainstorming Framework

A Claude Code skill for structured creative problem-solving and ideation. Provides proven brainstorming frameworks, lateral thinking techniques, and structured approaches to generate, evaluate, and refine ideas for product features, technical solutions, business strategies, and creative projects.

When to Use This Skill

Choose Ultimate Brainstorming Framework when:

• You need to generate creative solutions to a technical or business problem
• You want structured approaches to brainstorming beyond random ideation
• You need to evaluate and prioritize a set of ideas
• You want to break through creative blocks with lateral thinking techniques
• You're planning a brainstorming session for your team

Consider alternatives when:

• You need specific technical architecture decisions (use an architecture skill)
• You want product feature prioritization (use a product manager skill)
• You need marketing campaign ideas specifically (use a marketing ideas skill)

Quick Start

Copy
# Install the skill
claude install ultimate-brainstorming-framework

# Generate ideas
claude "Brainstorm 10 ways to reduce user churn in our SaaS product using the SCAMPER framework"

# Solve a problem
claude "Use the 5 Whys technique to analyze why our deployment pipeline takes 45 minutes"

# Evaluate ideas
claude "Evaluate these 8 feature ideas using an impact/effort matrix: [list ideas]"

Core Concepts

Brainstorming Frameworks

Framework	Approach	Best For
SCAMPER	Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse	Improving existing products
Six Thinking Hats	Parallel thinking from 6 perspectives	Group decision-making
How Might We	Reframe problems as opportunities	Design thinking
Crazy 8s	8 ideas in 8 minutes, sketch-based	Rapid visual ideation
First Principles	Break down to fundamentals, rebuild	Technical innovation
Reverse Brainstorming	"How could we make this worse?" then flip	Finding hidden problems

Ideation Process

1. Define → Clear problem statement
   "How might we reduce onboarding time from 15 minutes to 2 minutes?"

2. Diverge → Generate many ideas (no criticism)
   Quantity over quality. Wild ideas welcome.
   Target: 20+ ideas in 15 minutes.

3. Cluster → Group related ideas
   Find themes across individual ideas.

4. Converge → Select the best ideas
   Vote, score, or use a decision matrix.

5. Refine → Develop selected ideas
   Add detail, identify risks, plan next steps.

Evaluation Methods

Method	Dimensions	Output
Impact/Effort Matrix	Impact (high/low) × Effort (high/low)	2×2 quadrant placement
Dot Voting	Team preference	Ranked list
Feasibility/Desirability/Viability	Three lenses	Score per idea
RICE Scoring	Reach, Impact, Confidence, Effort	Numerical ranking
Pro/Con Analysis	Advantages vs. disadvantages	Balanced comparison

Configuration

Parameter	Type	Default	Description
framework	string	"scamper"	Framework: scamper, six_hats, hmw, first_principles, reverse
idea_count	number	10	Target number of ideas to generate
domain	string	"product"	Context: product, technical, business, creative
evaluation	string	"impact_effort"	Evaluation: impact_effort, rice, dot_vote, pro_con
constraints	string[]	[]	Constraints to work within

Best Practices

1. Separate divergent and convergent thinking — Don't evaluate ideas while generating them. The fastest way to kill creativity is saying "that won't work" during brainstorming. Generate first, evaluate second.

2. Start with a specific problem statement — "Make the product better" produces vague ideas. "Reduce time-to-first-value from 15 minutes to under 3 minutes for new users" produces actionable solutions.

3. Use constraints to drive creativity — "How would we solve this with zero budget?" or "How would we solve this if we had to launch in one week?" Constraints force creative thinking and often reveal simpler solutions.

4. Build on others' ideas — "Yes, and..." instead of "No, but...". Take someone's wild idea and ask "What would it take to make this work?" Often the best solutions come from combining and refining multiple ideas.

5. Document everything — Ideas generated but not captured are lost. Write down every idea during brainstorming, even the "bad" ones. Bad ideas often contain kernels of insight that lead to great solutions when revisited.

Common Issues

All ideas are incremental — You're anchoring on the current solution. Use First Principles thinking to break the problem down to fundamentals and rebuild from scratch. Or try Reverse Brainstorming: "How would we make onboarding take 2 hours?" Then flip every answer.

Group defaults to the loudest voice — Use silent ideation first (everyone writes ideas independently for 5 minutes) before group discussion. This ensures introverts contribute equally and prevents anchoring on the first idea spoken.

Ideas are too abstract to act on — After selecting ideas, force specificity: Who is this for? What's the first step? How would we measure success? What could go wrong? Ideas need detail to become actionable plans.