brainstorm · superclaude-org — Claude Code command for ideas and setup
brainstorm is a command for Claude Code, Codex, GitHub Copilot, and Gemini CLI that clarifies vague project ideas and turns them into requirements before planning.
MIT ★ 23,950 updated 2026-09-27
.claude/commands/brainstorm.mdWhat brainstorm does
Run /sc:brainstorm with a topic to clarify goals and examine feasibility across project areas. The command coordinates personas such as architect, analyst, frontend, and security, then produces requirements, user stories, acceptance criteria, and open questions.
You can choose systematic, agile, or enterprise strategies, set the exploration depth, or request parallel paths. The listed MCP servers are preferred tools, not prerequisites; the command can fall back to native reasoning and tools when a server is unavailable. Its scope ends at requirements: it does not produce architecture, database schemas, API contracts, or implementation code. The description points to /sc:design for architecture and /sc:workflow for implementation planning.
What it helps with
- clarify requirements behind an ambiguous product idea
- assess feasibility across project domains
- turn goals into user stories and acceptance criteria
- collect unresolved questions before architecture work
Example prompts for the agent
- Explore a project-management app idea and write its requirements:
/sc:brainstorm "project management app" --strategy systematic. - Review a collaboration feature through parallel frontend, backend, and security paths:
/sc:brainstorm "real-time collaboration" --strategy agile --parallel. - Assess an enterprise analytics concept and capture open questions:
/sc:brainstorm "enterprise analytics platform" --strategy enterprise.
How to install brainstorm
Manually: put the files in place
.claude/commands/brainstorm.mdCall it with /brainstorm. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/brainstorm.mdCall it with /prompts:brainstorm. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/brainstorm.prompt.mdManually: put the files in place
.gemini/commands/brainstorm.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about brainstorm
How do I install brainstorm in Claude Code?
Save the command file at .claude/commands/brainstorm.md.
What does the brainstorm command do?
It uses guided exploration to clarify a project idea and produces a requirements specification with goals, user stories, acceptance criteria, and open questions.
Does brainstorm generate architecture or code?
No. It stops after requirements discovery. The description directs architecture work to /sc:design and implementation planning to /sc:workflow.
Source text
brainstorm.md · MIT
--- name: brainstorm description: "Interactive requirements discovery through Socratic dialogue and systematic exploration" category: orchestration complexity: advanced mcp-servers: [sequential, context7, magic, playwright, morphllm, serena] personas: [architect, analyzer, frontend, backend, security, devops, project-manager] --- # /sc:brainstorm - Interactive Requirements Discovery > **Context Framework Note**: This file provides behavioral instructions for Claude Code when users type `/sc:brainstorm` patterns. This is NOT an executable command - it's a context trigger that activates the behavioral patterns defined below. ## Triggers - Ambiguous project ideas requiring structured exploration - Requirements discovery and specification development needs - Concept validation and feasibility assessment requests - Cross-session brainstorming and iterative refinement scenarios ## Context Trigger Pattern ``` /sc:brainstorm [topic/idea] [--strategy systematic|agile|enterprise] [--depth shallow|normal|deep] [--parallel] ``` **Usage**: Type this pattern in your Claude Code conversation to activate brainstorming behavioral mode with systematic exploration and multi-persona coordination. ## Behavioral Flow 1. **Explore**: Transform ambiguous ideas through Socratic dialogue and systematic questioning 2. **Analyze**: Coordinate multiple personas for domain expertise and comprehensive analysis 3. **Validate**: Apply feasibility assessment and requirement validation across domains 4. **Specify**: Generate concrete specifications with cross-session persistence capabilities 5. **Handoff**: Create actionable briefs ready for implementation or further development Key behaviors: - Multi-persona orchestration across architecture, analysis, frontend, backend, security domains - Advanced MCP coordination with intelligent routing for specialized analysis - Systematic execution with progressive dialogue enhancement and parallel exploration - Cross-session persistence with comprehensive requirements discovery documentation ## MCP Integration - **Sequential MCP**: Complex multi-step reasoning for systematic exploration and validation - **Context7 MCP**: Framework-specific feasibility assessment and pattern analysis - **Magic MCP**: UI/UX feasibility and design system integration analysis - **Playwright MCP**: User experience validation and interaction pattern testing - **Morphllm MCP**: Large-scale content analysis and pattern-based transformation - **Serena MCP**: Cross-session persistence, memory management, and project context enhancement - **Availability fallback**: The MCP servers named here are preferred tooling, not hard requirements — when one is not installed, degrade gracefully (native reasoning in place of Sequential, official docs via web lookup in place of Context7, native tools otherwise) instead of routing work to absent servers. ## Tool Coordination - **Read/Write/Edit**: Requirements documentation and specification generation - **TodoWrite**: Progress tracking for complex multi-phase exploration - **Task**: Advanced delegation for parallel exploration paths and multi-agent coordination - **WebSearch**: Market research, competitive analysis, and technology validation - **sequentialthinking**: Structured reasoning for complex requirements analysis ## Key Patterns - **Socratic Dialogue**: Question-driven exploration → systematic requirements discovery - **Multi-Domain Analysis**: Cross-functional expertise → comprehensive feasibility assessment - **Progressive Coordination**: Systematic exploration → iterative refinement and validation - **Specification Generation**: Concrete requirements → actionable implementation briefs ## Examples ### Systematic Product Discovery ``` /sc:brainstorm "AI-powered project management tool" --strategy systematic --depth deep # Multi-persona analysis: architect (system design), analyzer (feasibility), project-manager (requirements) # Sequential MCP provides structured exploration framework ``` ### Agile Feature Exploration ``` /sc:brainstorm "real-time collaboration features" --strategy agile --parallel # Parallel exploration paths with frontend, backend, and security personas # Context7 and Magic MCP for framework and UI pattern analysis ``` ### Enterprise Solution Validation ``` /sc:brainstorm "enterprise data analytics platform" --strategy enterprise --validate # Comprehensive validation with security, devops, and architect personas # Serena MCP for cross-session persistence and enterprise requirements tracking ``` ### Cross-Session Refinement ``` /sc:brainstorm "mobile app monetization strategy" --depth normal # Serena MCP manages cross-session context and iterative refinement # Progressive dialogue enhancement with memory-driven insights ``` ## Boundaries **Will:** - Transform ambiguous ideas into concrete specifications through systematic exploration - Coordinate multiple personas and MCP servers for comprehensive analysis - Provide cross-session persistence and progressive dialogue enhancement **Will Not:** - Make implementation decisions without proper requirements discovery - Override user vision with prescriptive solutions during exploration phase - Bypass systematic exploration for complex multi-domain projects ## CRITICAL BOUNDARIES **STOP AFTER REQUIREMENTS DISCOVERY** This command produces a REQUIREMENTS SPECIFICATION ONLY. **Explicitly Will NOT**: - Create architecture diagrams or system designs (use `/sc:design`) - Generate implementation code (use `/sc:implement`) - Make architectural decisions - Design database schemas or API contracts - Create technical specifications beyond requirements **Output**: Requirements document with: - Clarified user goals - Functional requirements - Non-functional requirements - User stories / acceptance criteria - Open questions for user **Next Step**: After brainstorm completes, use `/sc:design` for architecture or `/sc:workflow` for implementation planning.
© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework
Similar slash commands
All slash commands for Agent setup: memory, context, orchestration →brainstorm by other authors comes first.