brainstorming

# Brainstorming Skill **Design-first approach: no code before design approval.** --- ## Agent Workflow (MANDATORY) Before ANY brainstorming session, use `TeamCreate` to spawn agents: 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 steps) | | **Trivial fix (1-3 lines)** | Skip brainstorming, go to APEX | | **Simple rename/typo** | Skip brainstorming, go to APEX | --- ## 6-Step Process ### Step 1: Explore Project Context Gather context before asking questions: - `git log --oneline -20` - Recent changes and direction - Existing code patterns and conventions - Related documentation and prior decisions - Tech stack and dependency constraints ### Step 2: Ask Clarifying Questions (ONE AT A TIME) Ask focused questions sequentially. Wait for each answer before the next. Categories: purpose, constraints, success criteria, users, integrat...