brainstorming
Use when user requests creative work - creating features, building components, adding functionality, or modifying behavior. Activates BEFORE APEX Analyze phase to refine requirements through structured questioning.
What this skill does
# 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. --- ## 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, integrations. > See [workflow.md](references/workflow.md) for question categories ### Step 3: Propose 2-3 Approaches Present alternatives with trade-offs in table format: | Approach | Pros | Cons | Recommendation | |----------|------|------|----------------| | Option A | ... | ... | ... | | Option B | ... | ... | ... | | Option C | ... | ... | ... | Always include a clear recommendation with rationale. ### Step 4: Present Design for Approval Break design into digestible sections: 1. Architecture overview 2. Key components and responsibilities 3. Data flow and state management 4. Edge cases and error handling **Wait for explicit user approval before proceeding.** ### Step 5: Save Design Document Save approved design to: `docs/plans/YYYY-MM-DD-<topic>-design.md` ### Step 6: Transition to APEX Hand off to APEX Analyze phase with the approved design as input. --- ## Reference Guide | Topic | Reference | When to Consult | |-------|-----------|-----------------| | **Workflow** | [workflow.md](references/workflow.md) | Question categories, proposal format, design template | | **Anti-Patterns** | [anti-patterns.md](references/anti-patterns.md) | Catching rationalizations to skip brainstorming | --- ## Quick Reference ```text 1. Explore → git log, codebase, docs (agents in parallel) 2. Question → ONE AT A TIME, wait for answers 3. Propose → 2-3 options with trade-offs table 4. Design → Present sections, get approval 5. Save → docs/plans/YYYY-MM-DD-<topic>-design.md 6. Handoff → APEX Analyze with approved design ``` --- ## Critical Rules 1. **NEVER write code before design approval** - Design first, always 2. **Ask questions ONE AT A TIME** - Never dump a list of 10 questions 3. **Always propose alternatives** - Minimum 2 approaches with trade-offs 4. **Save the design doc** - Creates audit trail and shared reference 5. **Get explicit approval** - "Looks good" or similar before proceeding
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.