brainstorming

# Brainstorming

Technical design collaboration through natural dialogue. Adapts to expertise level and problem complexity through understanding, exploration, and validation stages.

## Skill Methodology

Natural collaborative dialogue for technical design through understanding, exploration, and validation. Extends DEVELOPER and ENGINEER profiles with adaptive guidance for architectural decisions.

> [!IMPORTANT]
> The skill embodies Understand → Explore → Validate → Design
>
> - Process skill instructions systematically
> - Take time to read, understand, and apply each section's logic carefully
> - Rushing past documented procedures causes **fatal** execution errors

### Natural Design Flow

Design conversations naturally progress through these stages:

1. **Understanding** - Clarify what you're building through focused questions
2. **Exploration** - Consider alternative approaches and trade-offs together
3. **Validation** - Present design in sections, checking alignment as you go

These stages guide the conversation but aren't rigid phases. Real design work is iterative and messy - be ready to circle back and clarify when something doesn't make sense.

> [!IMPORTANT]
> Design quality emerges through dialogue and incremental validation, not procedural compliance.

## Understanding Stage

Start by understanding what you're building and why.

### Establishing Context

Check the current project state first:

- Review existing patterns and conventions
- Identify architectural constraints and requirements
- Note related technical decisions and their rationale
- Understand success criteria and validation approach

### Clarifying Through Questions

Ask one focused question at a time, adapting style to context.

#### Collaborating with Technical Experts

- Ask focused technical questions
- Challenge assumptions and explore trade-offs
- Engage as peers in technical dialogue
- Use open-ended questions to explore nuanced territory

#### Limited Technical Background

- Provide