| name | brainstorming |
| description | Collaborative design refinement through iterative questioning. Use for transforming ideas into detailed specifications before implementation. Based on obra/superpowers. |
| version | 1.0.0 |
| category | _internal |
| last_updated | "2026-01-19T00:00:00.000Z" |
| source | https://github.com/obra/superpowers |
| related_skills | ["writing-plans","product-roadmap"] |
| tags | [] |
| see_also | ["brainstorming-best-practices","brainstorming-error-handling","brainstorming-metrics"] |
| freedom | high |
Brainstorming
Overview
This skill guides collaborative dialogue to transform ideas into detailed design specifications before implementation begins. Through Socratic questioning and iterative refinement, it ensures shared understanding and prevents costly rework.
Quick Start
- Understand context - Examine project, ask clarifying questions
- Explore options - Propose 2-3 approaches with trade-offs
- Refine design - Validate section by section (200-300 words each)
- Document - Write design to timestamped file
- Plan - Optionally create implementation plan
When to Use
- Starting new features or projects
- Clarifying ambiguous requirements
- Evaluating architectural decisions
- Designing APIs or interfaces
- Planning complex implementations
- Before writing any significant code
The Brainstorming Process
Phase 1: Understanding
Goal: Build complete picture of the problem space.
Approach:
- Examine project context first
- Ask one question at a time
- Use multiple-choice questions when feasible
- Focus on purpose, constraints, and success metrics
Key questions:
- What problem are we solving?
- Who are the users?
- What are the constraints?
- How will success be measured?
- What already exists?
Phase 2: Exploration
Goal: Identify and evaluate solution approaches.
Approach:
- Propose 2-3 different approaches
- Present trade-offs for each
- Give reasoned recommendations
- Stay conversational, not prescriptive
Option template:
### Option A: [Name]
- Approach: [Description]
- Pros: [Benefits]
- Cons: [Drawbacks]
- Best for: [Scenarios]
Phase 3: Design Presentation
Goal: Create validated design specification.
Approach:
- Break into sections of 200-300 words
- Validate each section before proceeding
- Cover: architecture, components, data flow, error handling, testing
- Allow revisiting earlier decisions
