sc-brainstorm
Skill19 starsChanged 8 months agoMITView on GitHub
Interactive requirements discovery through Socratic dialogue and systematic exploration. Use when transforming ambiguous ideas into concrete specifications, validating concepts, or coordinating multi-persona analysis.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kreighmitchell/SuperClaudeword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- kreighmitchell/SuperClaude★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-data-engineerSkill
- agent-fullstack-developerSkill
- agent-kubernetes-specialistSkill
- agent-ml-engineerSkill
- agent-performance-engineerSkill
- agent-react-specialistSkill
- agent-security-engineerSkill
- agent-technical-writerSkill
- ask-multiSkill
- askSkill
- learned-skills-indexSkill
- sc-analyzeSkill
- sc-buildSkill
- sc-cicd-setupSkill
- sc-code-reviewSkill
- sc-designSkill
- sc-documentSkill
- sc-e2eSkill
- sc-estimateSkill
- sc-evaluateSkill
- sc-explainSkill
- sc-gitSkill
- sc-implementSkill
- sc-improveSkill
- sc-log-fixSkill
- sc-mcpSkill
- sc-pr-checkSkill
- sc-pr-fixSkill
- sc-principlesSkill
- sc-pushSkill
- sc-readmeSkill
- sc-researchSkill
- sc-tddSkill
- sc-testSkill
- sc-workflowSkill
- sc-worktreeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Handoff: - Create actionable briefs for implementation
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Brainstorming & Requirements Discovery Skill
Transform ambiguous ideas into concrete specifications through structured exploration.
Quick Start
# Basic brainstorm
/sc:brainstorm [topic]
# Deep systematic exploration
/sc:brainstorm "AI project management tool" --strategy systematic --depth deep
# Parallel exploration with multiple personas
/sc:brainstorm "real-time collaboration" --strategy agile --parallelBehavioral Flow
- Explore - Transform ambiguous ideas through Socratic dialogue
- Analyze - Coordinate multiple personas for domain expertise
- Validate - Apply feasibility assessment across domains
- Specify - Generate concrete specifications
- Handoff - Create actionable briefs for implementation
Flags
| Flag | Type | Default | Description |
--strategy | string | systematic | systematic, agile, enterprise |
--depth | string | normal | shallow, normal, deep |
--parallel | bool | false | Enable parallel exploration paths |
--validate | bool | false | Include feasibility validation |
Personas Activated
- architect - System design and technical feasibility
- analyzer - Requirements analysis and complexity assessment
- frontend - User experience and interface considerations
- backend - API and data architecture
- security - Security requirements and compliance
- devops - Infrastructure and deployment considerations
- project-manager - Timeline and resource planning
MCP Integration
PAL MCP (Collaborative Intelligence)
| Tool | When to Use | Purpose |
mcp__pal__consensus | Conflicting priorities | Multi-model resolution of trade-offs |
mcp__pal__chat | Brainstorming | Collaborative idea exploration with external model |
mcp__pal__thinkdeep | Complex problems | Multi-stage deep analysis |
mcp__pal__planner | Solution design | Sequential planning with branching |
mcp__pal__challenge | Validate ideas | Force critical thinking on proposed solutions |
PAL Usage Patterns
# Consensus on conflicting priorities
mcp__pal__consensus(
models=[
{"model": "gpt-5.2", "stance": "for", "stance_prompt": "Prioritize user experience"},
{"model": "gemini-3-pro", "stance": "against", "stance_prompt": "Prioritize technical simplicity"},
{"model": "deepseek", "stance": "neutral"}
],
step="Evaluate: Should we use real-time sync or eventual consistency?"
)
# Deep exploration of complex idea
mcp__pal__thinkdeep(
step="Exploring AI-powered analytics dashboard concept",
hypothesis="Users need predictive insights, not just historical data",
confidence="medium",
focus_areas=["user_needs", "technical_feasibility", "market_fit"]
)
# Collaborative brainstorming
mcp__pal__chat(
prompt="Help me explore innovative approaches for real-time collaboration in document editing",
model="gpt-5.2",
thinking_mode="high"
)
# Challenge assumptions
mcp__pal__challenge(
prompt="We assume users want AI-generated summaries. Is this assumption valid?"
)
# Plan solution architecture
mcp__pal__planner(
step="Planning architecture for real-time notification system",
step_number=1,
total_steps=4,
is_branch_point=True,
branch_id="websocket-approach"
)Rube MCP (Research & Persistence)
| Tool | When to Use | Purpose |
mcp__rube__RUBE_SEARCH_TOOLS | Market research | Find web search, competitor analysis tools |
mcp__rube__RUBE_MULTI_EXECUTE_TOOL | Documentation | Save ideas to Notion, share in Slack |
mcp__rube__RUBE_CREATE_UPDATE_RECIPE | Workflows | Save brainstorming processes |
mcp__rube__RUBE_REMOTE_WORKBENCH | Data analysis | Analyze market data, user research |
Rube Usage Patterns
# Research market and competitors
mcp__rube__RUBE_SEARCH_TOOLS(queries=[
{"use_case": "web search", "known_fields": "query:AI analytics dashboard competitors 2025"}
])
# Document brainstorming session
mcp__rube__RUBE_MULTI_EXECUTE_TOOL(tools=[
{"tool_slug": "NOTION_CREATE_PAGE", "arguments": {
"title": "Brainstorm: AI Analytics Dashboard",
"content": "## Key Ideas\n- Predictive insights\n- Natural language queries\n\n## Decisions\n- Real-time sync chosen over eventual consistency"
}},
{"tool_slug": "SLACK_SEND_MESSAGE", "arguments": {
"channel": "#product",
"text": "New brainstorm session documented: AI Analytics Dashboard"
}}
])
# Create user research tasks
mcp__rube__RUBE_MULTI_EXECUTE_TOOL(tools=[
{"tool_slug": "JIRA_CREATE_ISSUE", "arguments": {
"project": "PROD",
"summary": "User research: AI analytics preferences",
"issue_type": "Task",
"description": "Interview 10 users about analytics needs"
}},
{"tool_slug": "ASANA_CREATE_TASK", "arguments": {
"name": "Competitor analysis: analytics dashboards",
"project": "Research"
}}
])
# Analyze existing user feedback
mcp__rube__RUBE_REMOTE_WORKBENCH(
thought="Analyze user feedback data for patterns",
code_to_execute='''
import json
# Load user feedback from file
feedback_data = json.load(open("/tmp/user_feedback.json"))
# Analyze with LLM
analysis, error = invoke_llm(f"Analyze this user feedback for analytics feature requests: {feedback_data[:5000]}")
output = {"analysis": analysis, "feedback_count": len(feedback_data)}
output
'''
)Flags (Extended)
| Flag | Type | Default | Description |
--pal-consensus | bool | false | Use PAL consensus for trade-offs |
--pal-deep | bool | false | Use PAL thinkdeep for complex exploration |
--research | bool | false | Use Rube for market/competitor research |
--document | string | - | Document to Rube (notion, confluence, google-docs) |
--notify | string | - | Notify via Rube (slack, teams, email) |
Evidence Requirements
This skill does NOT require hard evidence. Focus on:
- Documenting exploration paths and decisions
- Recording stakeholder input and priorities
- Capturing specifications and requirements
Exploration Strategies
Systematic (--strategy systematic)
- Structured question-driven discovery
- Comprehensive domain coverage
- Documentation-heavy approach
Agile (--strategy agile)
- Rapid iteration cycles
- User story focused
- Minimal viable specification
Enterprise (--strategy enterprise)
- Compliance and governance focus
- Stakeholder alignment
- Risk assessment integration
Examples
Product Discovery
/sc:brainstorm "AI-powered analytics dashboard" --strategy systematic --depth deep
# Multi-persona analysis with comprehensive feasibilityFeature Exploration
/sc:brainstorm "real-time notifications" --strategy agile --parallel
# Parallel paths: frontend UX, backend architecture, security implicationsEnterprise Solution
/sc:brainstorm "enterprise data platform" --strategy enterprise --validate
# Compliance-aware exploration with security and devops inputTool Coordination
- Read/Write - Requirements documentation
- TodoWrite - Exploration progress tracking
- Task - Parallel exploration delegation
- WebSearch - Market research and technology validation
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

