brainstorm

# Brainstorming Ideas Into Designs

## Overview

Transform vague ideas into concrete, implementable designs through structured dialogue.
Ask questions one at a time, present designs in digestible sections, and validate
incrementally before committing to implementation.

**Core principle:** One question at a time. Never overwhelm with multiple questions.

**Announce at start:** "I'm using the brainstorm skill to explore this idea."

## When to Use

- Starting a new feature or project
- Exploring design alternatives
- Clarifying requirements before implementation
- Breaking down complex problems
- Any creative work that modifies behavior

## The Process

### Phase 1: Understanding the Idea

**Before asking questions:**
1. Run `kodo query "<topic>"` to check existing patterns and context
2. Check project state (files, docs, recent commits)
3. Review any related learnings from past sessions

**Asking questions:**
- **One question per message** - If topic needs more exploration, break into multiple questions
- **Prefer multiple choice** when possible - easier to answer than open-ended
- Focus on: purpose, constraints, success criteria, edge cases
- If user gives vague answer, follow up to clarify

**Question types (prefer in this order):**
1. Multiple choice: "Which approach: A, B, or C?"
2. Yes/No confirmation: "Should it also handle X?"
3. Open-ended only when necessary: "What happens when...?"

### Phase 2: Exploring Approaches

When requirements are clear:
1. **Propose 2-3 approaches** with clear trade-offs
2. Lead with your recommendation and explain why
3. Present options conversationally, not as bullet lists
4. Wait for user to choose before proceeding

**Format:**
```
I'd recommend approach A because [reasoning].

Alternatively:
- Approach B would [trade-off]
- Approach C would [trade-off]

Which direction feels right?
```

### Phase 3: Presenting the Design

**Once approach is chosen:**
1. Present in sections of **200-300 words**
2. After each section ask: "Does