brainstorming

<objective> Brainstorming runs a design-first, no-code-before-approval process ahead of any non-trivial feature, component, or behavior change: explore project context, ask clarifying questions one at a time, diverge to 6-8 approaches via a named technique before converging on 2-3 with a trade-off table, present the design for explicit approval, save it to `docs/plans/`, then hand off to APEX Analyze along with the research already gathered (so Analyze doesn't repeat it). Skip it entirely for trivial fixes, typos, or simple renames -- those go straight to APEX. </objective> # Brainstorming Skill **Design-first approach: no code before design approval.** --- ## Agent Workflow (MANDATORY) Before ANY brainstorming session, spawn agents in parallel, one `Agent` call each with a `name`: 1. **fuse-ai-pilot:explore-codebase** - Understand project context, patterns, constraints 2. **fuse-ai-pilot:research-expert** - Fetch best practices and documentation After design approval, transition to **APEX Analyze** phase, **passing along the explore-codebase and research-expert findings** in the handoff (not just the design doc). APEX Analyze re-runs those same agents by default — carrying forward what was already gathered here avoids re-doing the same research twice. --- ## Overview | Scenario | Action | |----------|--------| | **New feature** | Full brainstorming (6 steps) | | **Major change** | Full brainstorming (6 steps) | | **Component creation** | Full brainstorming (6 step...