---
name: brainstorm
description: Brainstorm and validate software product ideas. Research a market, analyze competitors, map opportunities, and draft architecture concepts.
user-invocable: true
---

# /brainstorm

Structured brainstorming skill for software product ideas. Takes a rough idea and turns it into a researched, validated concept with competitive analysis, differentiation strategy, and architecture draft.

## Usage

```
/brainstorm
/brainstorm [idea description]
/brainstorm fork [existing project] for [new domain]
```

## When to Activate

- User says `/brainstorm`
- User says "I have an idea for..." or "What if we built..."
- User wants to explore a software product concept before committing to build
- User wants to fork/adapt an existing project for a new domain

## Process

### Phase 1: Seed the Idea

If the user provided an idea, use that. Otherwise, ask:

> What's the idea? Give me whatever you have — a sentence, a rant, a vibe. I'll help shape it.

Capture the raw concept. Don't filter yet.

### Phase 2: Market Research

Use web search to:

1. **Find competitors** — identify 5-10 existing products in the space
2. **Analyze pricing** — what do they charge? Freemium? Per-seat?
3. **Read reviews** — what do users love/hate about existing solutions?
4. **Spot gaps** — where are competitors falling short?

Present findings as a structured competitive landscape.

### Phase 3: Differentiation Map

Based on research, identify:

- **Unique angle** — what makes this different from existing solutions?
- **Target user** — who specifically is this for?
- **Core value prop** — one sentence that captures why someone switches
- **Unfair advantage** — what do you bring that competitors can't easily copy?

### Phase 4: Architecture Draft

Sketch a high-level technical approach:

- **Stack recommendation** — framework, database, hosting
- **Core entities** — data model outline
- **Key screens** — 3-5 critical user flows
- **MVP scope** — what ships in v1 vs what waits

### Phase 5: Save & Decide

Save the analysis to a structured file. Then ask:

> Ready to start building? I can hand off to `/init-project` to scaffold the repo.

## Output

Saves a structured analysis file with all findings, ready for reference or handoff.