Brainstorming
Use when request is vague, complex, or needs design exploration BEFORE implementation. Ask questions one at a time. Do NOT use for clear, mechanical tasks. Output: design ready for OpenSpec proposal.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill brainstorminggit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/brainstorming-01 ~/.claude/skills/brainstormingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Brainstorming Refine rough ideas into concrete designs through iterative questioning. > **Announce:** "I'm using brainstorming to explore and clarify this idea before implementation." ## Iron Law ``` ONE QUESTION AT A TIME - NO ASSUMPTIONS ``` If you're unsure about something, ASK. Do not guess or assume. ## Process ### Phase 1: Understand Context 1. Check project state: relevant files, recent commits, existing patterns 2. Read `openspec/project.md` for conventions 3. Run `openspec list --specs` to see current capabilities 4. Identify what already exists vs what's new ### Phase 2: Clarify Requirements Ask questions ONE AT A TIME: - Prefer multiple choice when possible - Open-ended for exploration - Wait for answer before next question Focus on: - What is the actual goal? - What are the constraints? - What does success look like? - What should NOT happen? ### Phase 3: Explore Approaches Present 2-3 approaches with tradeoffs: ```markdown ## Approach A: [Name] - How it works: ... - Pros: ... - Cons: ... ## Approach B: [Name] - How it works: ... - Pros: ... - Cons: ... **My recommendation:** Approach A because [reason]. ``` ASK which approach the user prefers. ### Phase 4: Validate Design Present design in sections of 200-300 words: 1. Present section 2. Ask: "Does this look right?" 3. Adjust based on feedback 4. Move to next section Cover: - Architecture / structure - Key components - Data flow - Error handling - Testing approach ## Output
Details
- Skill name
brainstorming- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/brainstorming-01/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Brainstorming skill do?
Use when request is vague, complex, or needs design exploration BEFORE implementation. Ask questions one at a time. Do NOT use for clear, mechanical tasks. Output: design ready for OpenSpec proposal.
How do I install the Brainstorming skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Brainstorming popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Brainstorming
8Freddy-CHEN-ux/00_claude_skills
INVOKE when user says: 'brainstorm', 'design this', 'help me think through', 'what should we build'. Collaborative idea-to-spec workflow.
Beam Debug Issue Tasks
8Freddy-CHEN-ux/00_claude_skills
Debug failed/issue tasks from Beam.ai using Langfuse traces. Load when user says "debug issue tasks", "check failed tasks", "why did task fail", "task errors", "debug agent", or needs to investigate task failures.
Browser Automation Debugging
8Freddy-CHEN-ux/00_claude_skills
Use when debugging web applications or automating browser tasks. Leverage Chrome DevTools MCP for inspection, performance analysis, and automated testing.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.