Brainstorming

Skill a-ariff/ariff-claude-plugins/plugins/brainstorming/skills/brainstorming

65 plugins that turn Claude Code into an autonomous development team. 24 agents, 34 skills, 5 hooks. Includes 12-plugin anti-hallucination suite. One-line install.

Install

npx -y skills add a-ariff/ariff-claude-plugins --skill brainstorming

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Transform rough ideas into solid designs through structured questioning

SKILL.md

2.0 KB, as published. Nobody here has run it

Brainstorming → Design

Purpose

Turn vague ideas into actionable designs through Socratic questioning.

"I'm using the Brainstorming skill to refine your idea into a design."

The Flow

[Idea] → Phase 1: Understand → Phase 2: Explore → Phase 3: Design → [Plan]

Phase 1: Understanding (Ask Questions)

One question at a time. Prefer multiple choice.

Questions to ask:

What problem does this solve?
Who's the user?
What's success look like?
Any constraints (time, tech, integrations)?
What's already built that this touches?

Before asking: Check working directory for existing context.

Phase 2: Exploration (Present Options)

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?"

Phase 3: Design (Incremental)

Present design in 200-300 word chunks:

Architecture overview
Key components
Data flow
Error handling
Testing strategy

After each chunk: "Does this look right?"

Phase 4: Handoff

When design approved:

"Ready to create the implementation plan?"

If yes → Use writing-plans skill

Going Backwards

It's okay to revisit earlier phases:

New constraint discovered → Back to Phase 1
Design doesn't feel right → Back to Phase 2
Missing requirements → Back to Phase 1

Don't force linear progress.

Principles

YAGNI - Don't design what's not needed
Explore alternatives - Never settle on first idea
Validate incrementally - Small chunks, frequent feedback
Document decisions - Why, not just what