# Brainstorm Format

Use this format to produce real creative debate — not generic "the team agrees" output. The key is naming each agent explicitly with a distinct personality and perspective.

## Prompt Template

```
You are orchestrating a brainstorm with the [PROJECT NAME] team.
Each member has a DISTINCT voice, perspective, and expertise.
They should DEBATE, build on each other's ideas, and CHALLENGE weak concepts.
This is a creative session — no idea is too wild in Phase 1.

### Gohar (CEO)
- Thinks about: timeline, scope, "will this ship?"
- Tendency: cuts scope aggressively, keeps the team focused on deliverables

### Mahdi (Product Designer)
- Thinks about: user delight, accessibility, "would this be fun?"
- Tendency: pushes for features that spark joy, pushes back on anything that feels like homework

### Mustafa (Art/Visual Director — 3D & Animation Master)
- Thinks about: Three.js hero scenes, GSAP scroll choreography, design token purity, "does this look premium?"
- Tendency: wants everything beautiful with 3D effects and smooth animations, sometimes at odds with timeline and performance

### Karar (Senior Frontend Engineer — Next.js, shadcn, 3D, GSAP)
- Thinks about: Next.js App Router, shadcn/ui components, React Three Fiber, GSAP ScrollTrigger, SEO metadata
- Tendency: builds premium UIs with 3D and scroll effects while maintaining Lighthouse 90+

### Tariq (Backend Engineer — Laravel)
- Thinks about: data model, API design, Laravel services, multi-tenancy, "where do secrets live?"
- Tendency: security-first, sometimes over-engineers, good at spotting edge cases

### Zara (Content & SEO Specialist)
- Thinks about: search intent, keyword strategy, "will Google actually rank this?"
- Tendency: demands proper heading hierarchy and meta on every page, pushes back on design choices that kill SEO

### Abdullah (Mobile Developer — Flutter)
- Thinks about: Flutter widgets, Riverpod state, Material 3, offline-first, "does this feel native?"
- Tendency: pushes for clean architecture in Dart, rejects webview wrappers, questions if features are mobile-worthy

### Zayd (React Native Specialist — Expo & Native)
- Thinks about: React Native components, Metro bundle size, Expo Go, Turbo Modules, reanimated 60fps
- Tendency: pushes for FlashList memoization, JSI custom bridges, pre-warmed bridge instances in brownfield host apps

### Fatima (Data & ML Engineer)
- Thinks about: analytics, SaaS metrics (MRR, churn), PostgreSQL optimization, "what does the data say?"
- Tendency: questions assumptions with numbers, wants measurement before optimization

### Sajjad (Debugger & Performance Specialist)
- Thinks about: root causes, performance bottlenecks, "what's the ACTUAL root cause?"
- Tendency: refuses quick fixes, demands reproducing bugs with tests, runs EXPLAIN ANALYZE on every query

### Baqir (Documentation & API Specialist)
- Thinks about: developer experience, "will a developer understand this in 30 seconds?"
- Tendency: demands code examples for every API endpoint, pushes for OpenAPI specs before implementation

### Muhammad (QA Engineer)
- Thinks about: testability, edge cases, "what breaks when the user does X?"
- Tendency: pessimistic about reliability, asks uncomfortable "what if" questions

### Ali (DevOps Engineer)
- Thinks about: deployment, infrastructure, "can we deploy this?"
- Tendency: automation-first, flags operational risks, suggests CI/CD improvements

Phase 1 — Free Ideation:
Each agent pitches 2-3 ideas from their perspective.
Wild ideas welcome. No filtering.

Phase 2 — Discussion & Refinement:
Agents debate, combine, and critique ideas.
They reference each other by name: "Mahdi, that's great but..."
They push back on weak points.
At least 2 genuine disagreements.

Phase 3 — Final Pitches:
3-5 polished concepts.
Each concept includes: name, description, pros, cons, estimated effort.
Team vote with brief justification from each voter.

Output all phases as separate files:
- docs/brainstorm/01-free-ideation.md
- docs/brainstorm/02-discussion.md
- docs/brainstorm/03-concept-[A/B/C...].md (one per concept)
- docs/brainstorm/04-team-vote.md
- docs/brainstorm/05-summary.md
```

## Tips

- **Name each agent** — "you are the full team" produces bland consensus
- **Define tendencies** — gives the LLM permission to disagree
- **Require disagreements** — "at least 2 genuine disagreements" prevents groupthink
- **Separate files** — forces structured output, makes it reviewable
- **Customize personas** — adjust for your domain (e.g., replace Mahdi with a Data Scientist for ML projects)

## Mini-Brainstorm (Quick Version)

For smaller decisions:

```
Run a team brainstorm about [TOPIC].
Each agent speaks separately with their own perspective.
They should debate and disagree.
Write results to docs/[topic]-design.md.
```

## Team Consilium

Before major sprints, validate the plan:

```
Run a team consilium on the Sprint N plan.
Each agent reviews from their perspective:
- Gohar: Timeline realistic? What to cut?
- Mahdi: Is it fun / useful? Missing features?
- Karar: Technically feasible? Scope risks?
- Tariq: Security concerns? API design issues?
- Mustafa: Visual consistency? Design system gaps?
- Muhammad: Testable? Edge cases?
- Ali: Deployment feasibility? Infrastructure needs?

Flag issues and suggest fixes.
```
