How this skill is triggered — by the user, by Claude, or both
Slash command
/brainstorming:brainstormingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
---
Turn vague ideas into actionable designs through Socratic questioning.
"I'm using the Brainstorming skill to refine your idea into a design."
[Idea] → Phase 1: Understand → Phase 2: Explore → Phase 3: Design → [Plan]
One question at a time. Prefer multiple choice.
Questions to ask:
Before asking: Check working directory for existing context.
Present 2-3 approaches:
### Approach A: [Name]
- Architecture: [how it works]
- Pros: [benefits]
- Cons: [tradeoffs]
- Complexity: [low/medium/high]
### Approach B: [Name]
...
Ask: "Which approach resonates? Or should we explore others?"
Present design in 200-300 word chunks:
After each chunk: "Does this look right?"
When design approved:
"Ready to create the implementation plan?"
If yes → Use writing-plans skill
It's okay to revisit earlier phases:
Don't force linear progress.
npx claudepluginhub a-ariff/ariff-claude-plugins --plugin brainstormingRefines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation before writing code or plans.
Transforms vague ideas into validated designs for features, architecture, or behavior via structured dialogue and review before implementation.