Should I use this for simple bug fixes?

No, you should skip brainstorming for tasks with obvious solutions, urgent production fixes, or when the user has already provided a specific design.

Can I return to an earlier phase if my requirements change?

Yes, the skill is non-linear. You can go back to the Understanding or Exploration phases whenever new information or constraints emerge.

Does this skill help with documentation?

While its primary focus is the thought process, it provides templates for Architecture Decision Records (ADRs) and design docs to capture the final results.

When should I use the Brainstorming skill in Claude Code?

Use this skill at the beginning of any development task where the requirements are not crystal clear or where there are multiple ways to solve a problem.

How does the skill handle architectural decisions?

It proposes 2-3 different approaches with a comparison of pros, cons, and complexity, allowing you to make an informed choice via structured prompts.

Structured Brainstorming

Name: Structured Brainstorming
Author: yonatangross

byyonatangross

•

Productivity & Workflow

Transforms rough ideas into fully-formed technical designs through guided Socratic questioning and architectural alternative exploration.

About

The Brainstorming skill is a specialized framework for Claude Code that prevents premature implementation by enforcing a structured three-phase design process: Understanding, Exploration, and Presentation. It uses Socratic questioning to uncover hidden constraints and 'YAGNI' principles to avoid over-engineering. By presenting architectural alternatives with explicit trade-offs and validating designs in incremental sections, this skill ensures that developers and AI are perfectly aligned on the purpose, constraints, and technical approach before the first line of code is written.

Key Features

Socratic questioning templates for purpose and constraint discovery
Three-phase guided workflow (Understanding, Exploration, Design Presentation)
29 GitHub stars
Multi-option architectural comparison with explicit trade-off matrices
Incremental design validation to prevent project misalignment
Integration with ADRs and testing strategy builders

Use Cases

Evaluating trade-offs between different tech stacks, data models, or communication protocols
Refining vague product ideas into concrete, actionable implementation plans
Defining technical architecture for new features with multiple implementation paths

About

Key Features

Socratic questioning templates for purpose and constraint discovery
Three-phase guided workflow (Understanding, Exploration, Design Presentation)
29 GitHub stars
Multi-option architectural comparison with explicit trade-off matrices
Incremental design validation to prevent project misalignment
Integration with ADRs and testing strategy builders

Use Cases

Evaluating trade-offs between different tech stacks, data models, or communication protocols
Refining vague product ideas into concrete, actionable implementation plans
Defining technical architecture for new features with multiple implementation paths