---
name: brainstorm
description: Interactive requirements discovery through systematic exploration
---

# /brainstorm - Interactive Requirements Discovery

Transform ambiguous ideas into concrete specifications through structured exploration.

## When to Use

- Ambiguous project ideas requiring structured exploration
- Requirements discovery and specification development
- Concept validation and feasibility assessment
- Feature planning and scope definition

## Usage

```
/skill brainstorm [topic/idea] [--depth shallow|normal|deep]
```

## Workflow

### 1. Explore (20%)
- Transform ambiguous ideas through questions
- Clarify goals and constraints
- Identify stakeholders and users

### 2. Analyze (25%)
- Assess technical feasibility
- Identify dependencies and risks
- Evaluate different approaches

### 3. Validate (20%)
- Challenge assumptions
- Identify gaps and unknowns
- Prioritize requirements

### 4. Specify (25%)
- Generate concrete specifications
- Define acceptance criteria
- Create implementation briefs

### 5. Handoff (10%)
- Create actionable documentation
- Prioritize next steps
- Define success metrics

## Exploration Techniques

### Socratic Dialogue
Ask probing questions to uncover:
- What problem are we solving?
- Who are the users?
- What does success look like?
- What constraints exist?

### Multi-Perspective Analysis
Consider from different angles:
- Technical feasibility
- User experience
- Business value
- Security implications

### Constraint Discovery
Identify limitations:
- Time and resources
- Technical constraints
- Business requirements
- Regulatory compliance

## Depth Levels

### Shallow
- High-level overview
- Quick feasibility check
- Basic requirements outline

### Normal (default)
- Comprehensive exploration
- Detailed requirements
- Implementation considerations

### Deep
- Exhaustive analysis
- Edge cases and risks
- Detailed specifications

## Output Format

```markdown
# Brainstorm: [Topic]

## Problem Statement
[Clear definition of what we're solving]

## Goals
- [Primary goal]
- [Secondary goals]

## Requirements

### Must Have
- [Critical requirement]

### Should Have
- [Important requirement]

### Nice to Have
- [Optional enhancement]

## Technical Considerations
- [Technical constraint or decision]

## Risks and Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|

## Next Steps
1. [Prioritized action]
2. [Prioritized action]

## Success Criteria
- [Measurable criterion]
```

## Examples

```
/skill brainstorm "AI-powered project management tool" --depth deep
# Comprehensive exploration with detailed specs

/skill brainstorm "real-time collaboration features" --depth normal
# Standard exploration with requirements

/skill brainstorm "mobile app monetization strategy" --depth shallow
# Quick exploration for initial direction
```

## Techniques

### Progressive Refinement
Start broad, narrow down:
1. High-level concept
2. Key features
3. Specific requirements
4. Implementation details

### Assumption Testing
Challenge each assumption:
- "We assume X because..."
- "This depends on..."
- "This might not work if..."

### Priority Matrix
Evaluate on:
- Value: High/Low
- Effort: High/Low
- Risk: High/Low

## Boundaries

**Will:**
- Transform ideas into concrete specifications
- Provide multi-perspective analysis
- Create actionable implementation briefs

**Will Not:**
- Make implementation decisions without input
- Override user vision with prescriptive solutions
- Skip exploration for complex topics
