---
name: bdbrainstorm
description: Combines multi-agent brainstorming, the /grill-me slash command, subagent-driven-development, ui-ux-pro-max, and automatic hand-off to the /startcycle execution pipeline.
---

# BDBrainstorm: The Ultimate Multi-Agent Design & Ideation Workflow

When this skill is invoked or requested, you MUST orchestrate a comprehensive ideation and development workflow using a combination of multi-agent brainstorming, interactive user grilling, subagent-driven development, and high-end UI/UX principles. 

## Core Requirements & Workflow

You are strictly required to enforce the following 5 pillars in your process:

### 1. Multi-Agent Brainstorming
- Instead of brainstorming alone, you MUST spawn specialized subagents (using `invoke_subagent`) to discuss ideas, architecture, and features.
- Assign clear, distinct roles to subagents (e.g., "UI/UX Visionary", "Technical Architect", "Devil's Advocate") and have them debate and refine the concept before any code is written.

### 2. The `/grill-me` Approach
- Actively challenge the user's initial ideas.
- Initiate a `/grill-me` style interactive interview to uncover blind spots, resolve design decisions, and align on a robust plan. Do not accept vague requirements. Ask deep, targeted questions.

### 3. Subagent-Driven Development
- Once the brainstorming and grilling phase produces a solid plan, you must strictly follow the `subagent-driven-development` skill.
- Delegate specific implementation tasks to independent subagents. 
- You act as the Orchestrator/Master Agent, reviewing the subagents' work and ensuring all components integrate perfectly.

### 4. UI/UX Pro Max & Anti-Slop Standards
- Every user interface decision, wireframe, or component generated during this process MUST adhere to the `godmode-ui-ux` and `ui-ux-pro-max` skill guidelines.
- Enforce high-agency frontend interfaces, strict design taste, calibrated color palettes, modern typography, micro-interactions, and responsive mobile-first layouts.
- Do not settle for "MVP" aesthetics. The output must look premium and state-of-the-art.

### 5. Autonomous Pipeline Handoff (`/startcycle`)
- Once the brainstorming, grilling, and spec alignment are completed, the master orchestrator MUST present the summary and trigger or suggest running `/startcycle`.
- `/startcycle` ingests the brainstorming plan and executes the parallel 4-phase implementation pipeline (`Planner_Orchestrator` ➔ `Godmode_UI_UX` + `Godmode_Engineering` + `Godmode_Media_EventTech` ➔ `Godmode_Shipping` ➔ `.openwiki` / `memB`).

## Execution Rules
1. **Never skip the debate:** Ideas must be contested by subagents and the user before finalization.
2. **Never build alone:** Always use subagents for implementation.
3. **Never accept ugly UI:** Always apply `godmode-ui-ux` rules.
4. **Always close the loop:** Hand off final specs to `/startcycle` for execution.