agentleFS
excattexcatt/superclaude-plusplus/skills/brainstorm/SKILL.md

brainstorm

Skill14 starsChanged 37 days agoMITView on GitHub

Interactive requirements discovery through Socratic dialogue and systematic exploration

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report, team-polish and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 9 projects that use this

  • CoralGameSkill

    team-polish

    Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

    Also in 11 projects that use this

  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 6 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 6 projects that use this

  • +8 more from CoralGame

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Distinctive:

    Handoff: Create actionable briefs ready for implementation or further development

    line 29

“Common” is measured: kept by at least 6 in 10 of the 156 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interactive Requirements Discovery

Context Framework Note: This file provides behavioral instructions for Claude Code when users type /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

/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

Interview Discipline

이 세 행동 규칙은 mattpocock/skills (MIT)의 grill-me 스킬에서 흡수되었다. 다중 페르소나 분석을 보강하는 대화 규율 이며, 새 스킬을 만들지 않고 /brainstorm에 통합되어 있다.

  1. 한 번에 한 질문 (One question at a time) — 사용자의 답변을 받기 전에는 다음 질문으로 넘어가지 않는다. 여러 질문을 묶어서 던지지 않는다.
  2. 추천답 동반 (Recommended answer per question) — 각 질문마다 합리적인 추천 답변을 함께 제시한다. 사용자가 "yes"만으로 진행할 수 있게 하여 대화 비용을 낮춘다.
  3. 코드 우선 탐색 (Codebase first, ask second) — 코드베이스 탐색으로 답할 수 있는 질문은 사용자에게 묻지 말고 직접 grep/Read로 답을 찾는다.

See Also

  • /grill-with-docs — 기존 도메인 모델에 대한 stress-test가 필요할 때. /brainstorm은 새 기능 요구사항 탐색에, /grill-with-docs는 기존 도메인 어휘·결정과의 정합성 점검에 사용한다.

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

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

/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

/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

/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

/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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.