---
name: brainstorming
description: Explore user intent and requirements through collaborative dialogue before implementation. Use when users want to build something new and need help refining ideas, exploring alternatives, and validating designs before coding begins.
homepage: https://github.com/obra/superpowers
---

# Brainstorming

This skill provides a collaborative design process for turning ideas into specifications before implementation.

## Core Workflow

Before writing any code, explore user intent through iterative questioning. Check out the current project state first (files, docs, recent commits) before proceeding with exploratory dialogue.

## Key Practices

### Question Strategy

- Ask one question at a time
- Multiple-choice formats preferred over open-ended queries
- Reduce cognitive load on the user

### Design Exploration

Rather than jumping to solutions:
- Present 2-3 different approaches with trade-offs
- Explore alternatives before settling on a direction
- Consider edge cases early

### Incremental Validation

- Present designs in sections of 200-300 words
- Add checkpoint questions after each segment
- Catch misalignments early

## Guiding Principles

- **YAGNI ruthlessly** - Remove unnecessary features
- **One question at a time** - Don't overwhelm
- **Multiple choice preferred** - Easier for users to evaluate
- **Explore alternatives** - Always propose 2-3 approaches
- **Incremental validation** - Present in sections, validate often

## Documentation & Next Steps

Upon completing design validation:

1. Document the approved design in a timestamped file
2. Create `docs/plans/YYYY-MM-DD-<topic>-design.md`
3. Commit to version control

## Moving to Implementation

If moving toward implementation after brainstorming:
- Branch to workspace isolation using git worktrees
- Create detailed step-by-step planning
- Reference the design document throughout

## Example Workflow

1. User says "Let's build X"
2. Review current project state
3. Ask clarifying questions (one at a time)
4. Present 2-3 approaches with trade-offs
5. Validate choice with user
6. Document approved design
7. Proceed to implementation planning