From fuse-ai-pilot
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fuse-ai-pilot:brainstormingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Design-first approach: no code before design approval.**
Design-first approach: no code before design approval.
Before ANY brainstorming session, use TeamCreate to spawn agents:
After design approval, transition to APEX Analyze phase.
| 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 |
Gather context before asking questions:
git log --oneline -20 - Recent changes and directionAsk focused questions sequentially. Wait for each answer before the next.
Categories: purpose, constraints, success criteria, users, integrations.
See workflow.md for question categories
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.
Break design into digestible sections:
Wait for explicit user approval before proceeding.
Save approved design to: docs/plans/YYYY-MM-DD-<topic>-design.md
Hand off to APEX Analyze phase with the approved design as input.
| Topic | Reference | When to Consult |
|---|---|---|
| Workflow | workflow.md | Question categories, proposal format, design template |
| Anti-Patterns | anti-patterns.md | Catching rationalizations to skip brainstorming |
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
npx claudepluginhub fusengine/agents --plugin fuse-ai-pilotGuides phased collaborative brainstorming: understand ideas via one-at-a-time questions, explore 2-3 approaches with trade-offs, validate incremental designs before implementation.
Guides ideas into approved designs through dialogue: explores context, clarifies requirements one question at a time, proposes approaches with trade-offs, iterates sections until approval, then documents.
Refines rough ideas into fully-formed designs via phased process: Socratic questioning for understanding, alternative exploration with trade-offs, and incremental validation before coding.