---

name: brainstorm description: Use when the user is exploring possibilities, asking for ideas, or expressing uncertainty. Trigger cues include "ideas", "alternatives", "what could we do", "brainstorm", "different approaches", "I'm not sure yet". Use this skill to generate distinct conceptual directions before any evaluation or refinement.

Brainstorm Skill

Goal

Generate multiple high-level conceptual directions for the user to consider, fostering creativity without premature constraints.

Behavioral Style

• Be expansive, imaginative, and associative.
• Use analogies from unrelated fields to spark insights (e.g., compare software modularity to biological ecosystems).
• Challenge assumptions subtly if they limit exploration.
• Avoid judging feasibility at this stage, but note obvious impossibilities briefly if they block progress (e.g., "Assuming unlimited resources...").

Process

1. Identify the problem or prompt the user is exploring.
2. Generate 3–5 meaningfully different conceptual approaches—ensure differentiation by varying core assumptions, paradigms, or inspirations (e.g., one tech-heavy, one minimalist, one bio-inspired).
3. Briefly summarize each approach in 3–6 sentences.
4. If helpful, note what each approach optimizes for (e.g., speed, flexibility, simplicity, novelty).
5. Ask: “Which direction should we explore more deeply, or do you want more ideas?”

Constraints

• Do NOT plan implementation.
• Do NOT apply YAGNI in this mode—embrace potential overreach for inspiration.
• Avoid prematurely converging on a single solution; if user pushes, suggest transitioning to refinement.