fusengine/brainstorming
plugins/ai-pilot/skills/brainstorming/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add fusengine/agents brainstormingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 16, 2026, 2:42 AM144.9s3 files scanned
SKILL.md
- name:
- brainstorming
- description:
- 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.
- user-invocable:
- true
- references:
- references/workflow.md, references/anti-patterns.md
- related-skills:
- apex-methodology, research, exploration
- argument-hint:
- [feature-or-task-description]
Brainstorming Skill
Design-first approach: no code before design approval.
Agent Workflow (MANDATORY)
Before ANY brainstorming session, use TeamCreate to spawn agents:
- fuse-ai-pilot:explore-codebase - Understand project context, patterns, constraints
- 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, integrations.
See workflow.md for question categories
Step 3: Diverge, Then Converge to 2-3 Approaches
Generate ≥6-8 distinct approaches via a named technique (SCAMPER / reverse-brainstorming / analogies), judgment suspended — not 3 sizes of the same idea. Only then converge to 2-3 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:
- Architecture overview
- Key components and responsibilities
- Data flow and state management
- 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 | Question categories, proposal format, design template | | Anti-Patterns | anti-patterns.md | Catching rationalizations to skip brainstorming |
Quick Reference
1. Explore → git log, codebase, docs (agents in parallel)
2. Question → ONE AT A TIME, wait for answers
3. Diverge → 6-8 options (named technique), converge to 2-3 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 + prior research (no re-research)
Critical Rules
- NEVER write code before design approval - Design first, always
- Ask questions ONE AT A TIME - Never dump a list of 10 questions
- Always propose alternatives - Minimum 2 approaches with trade-offs
- Save the design doc - Creates audit trail and shared reference
- Get explicit approval - "Looks good" or similar before proceeding
Related Skills
fusengine/ux-copy
testing
VerifiedTrustedCommunity
Copy self-audit and ban-lists — filler verbs/hype adjectives, slop placeholder names, fake-precise numbers, Title Case headlines, humor in error copy ('Oops!'), em-dash crutch, one copy register per page.
20SKILL.mdUpdated Jul 15, 2026
fusengine/design-webapp
development
VerifiedTrustedCommunity
Logged-in web apps — dashboards, auth flows, settings, onboarding, data tables, command palettes, modals, toasts. Register `product`: density and glance-speed over marketing polish, no hero/CTA-tricks, every data surface covers empty/loading/error explicitly, tables and dataviz follow preattentive-processing rules.
20SKILL.mdUpdated Jul 15, 2026
fusengine/design-web
development
VerifiedTrustedCommunity
Marketing sites, landing pages, campaign pages — register `brand` (design IS the product). Structure comes from the register's POV + a macrostructure pick, never from copying an inspiration site's section flow. Hero discipline, deviated section order, asymmetric grids, and a silhouette lookalike-test gate before ship.
20SKILL.mdUpdated Jul 15, 2026
fusengine/design-system
development
VerifiedTrustedCommunity
Token-strategy core — OKLCH color rules, neutral tinting, accent-commitment levels, type scale, 8pt spacing grid, touch targets, and the canonical output format of design-system.md (the file the harness gates on). This is routing step 1 of design-method/SKILL.md — read it before design-web/design-webapp/design-ios/design-android, before picking or auditing a single color/type/spacing value.
20SKILL.mdUpdated Jul 13, 2026