/brainstorm — 아이디어를 짜내는 회의 진행자#
| 항목 | 내용 |
|---|---|
| 실행 명령 | /cc-product:brainstorm |
한마디로#
머릿속에 흩어진 생각을 검증된 아이디어 회의 기법으로 끌어내고 정리해 주는 진행자입니다. 혼자 막막하게 고민하는 대신, 노련한 퍼실리테이터가 옆에서 질문을 던지고 결과를 표로 깔끔하게 묶어 준다고 보면 됩니다.
누가·언제 쓰나요#
- "이 기능에 어떤 아이디어를 넣을까?", "이 문제를 어떻게 풀까?" 처럼 아이디어가 더 필요할 때
- 새 기능 아이디어 발굴, 특정 문제의 해결책 찾기, 아키텍처 대안 탐색, 프로세스 개선, 마케팅 전략, 리스크 대응책 마련 등 거의 모든 단계에서 쓸 수 있습니다.
- 보통 한 번 진행에 15~45분 정도 걸립니다.
무엇을 해주나요#
회의가 끝나면 하나의 정리 문서가 파일로 저장됩니다 (brainstorming-{주제}-{날짜}.md). 그 안에는:
- 나온 아이디어 전부 — 카테고리별로 묶고 중복은 정리
- 핵심 인사이트 3~7개 — 영향력·실현 가능성 기준으로 추린 알짜
- 통계 — 아이디어 개수, 카테고리 수, 사용한 기법
- 다음 단계 추천 — 주제에 맞는 다음 작업 안내
어떻게 쓰나요#
# 아이디어 회의 시작
/brainstorm
명령을 실행하면 진행자가 차례로 세 가지를 물어봅니다.
- 무엇을 브레인스토밍할지 (주제)
- 어떤 상황인지 (현재 단계, 예산·일정·기술 제약, 이전에 시도한 것, 성공 기준)
- 원하는 결과물 (예: 기능 아이디어 20개 이상, 실현 가능한 해결책 3~5개)
이후엔 답변만 따라가면 됩니다. 주제에 맞는 기법을 골라 진행자가 알아서 이끌어 줍니다.
안에서 무슨 일이 벌어지나요#
총 8단계로 진행되며, 한 단계씩 차근차근 밟습니다.
- 목표 정하기 — 주제·상황·원하는 결과를 질문으로 명확히 합니다.
- 기법 고르기 — 주제에 맞는 검증된 회의 기법을 2~3개 선택합니다. (예: 근본 원인을 파는 "5 Whys", 다양한 시각으로 보는 "Six Thinking Hats", 강점·약점을 따지는 "SWOT" 등)
- 기법 실행 — 고른 기법을 하나씩 체계적으로 적용하며 떠오른 아이디어를 빠짐없이 기록합니다.
- 아이디어 정리 — 모든 기법에서 나온 아이디어를 카테고리로 묶고 중복을 합칩니다.
- 핵심 인사이트 뽑기 — 영향력이 크고 실현 가능하며 핵심 목표를 건드리는 알짜 3~7개를 추립니다.
- 결과 문서 생성 — 위 내용을 하나의 마크다운 문서로 만들어 저장합니다.
- 상태 업데이트 — 진행 기록을 워크플로 상태 파일에 남깁니다.
-
다음 단계 추천 — 주제에 맞는 다음 작업(예: 기능 아이디어면
/prd, 해결책 탐색이면/architecture)을 안내합니다.
⚙️ 상세 옵션·실행 명세 (개발자 / AI 에이전트용)
Workflow Overview#
Goal: Generate creative ideas and solutions using structured brainstorming techniques
Phase: Cross-phase (supports all BMAD phases)
Agent: Creative Intelligence
Inputs: Brainstorming objective, context, constraints
Output: Structured brainstorming document with ideas, insights, and recommendations
Duration: 15-45 minutes
Pre-Flight#
- Load context per
helpers.md#Combined-Config-Load - Explain purpose:
"I'll facilitate a structured brainstorming session using proven creative techniques. This generates comprehensive ideas and actionable insights."
Brainstorming Process#
Use TodoWrite to track: Define Objective → Select Techniques → Execute Brainstorming → Organize Ideas → Extract Insights → Generate Output → Update Status
Part 1: Define Objective#
Ask user:
Q1: Brainstorming Topic
"What are we brainstorming?"
Examples:
- Feature ideas for a product
- Solutions to a specific problem
- Architecture alternatives
- Process improvements
- Marketing strategies
- Risk mitigation approaches
Store as: {{objective}}
Q2: Context
"What's the context?"
Provide:
- Current project phase
- Existing constraints (budget, timeline, technology)
- What's been tried before
- Success criteria
Store as: {{context}}
Q3: Desired Outcome
"What's the desired outcome?"
Examples:
- List of 20+ feature ideas
- 3-5 viable solutions
- Risk identification
- Creative alternatives to current approach
Store as: {{desired_outcome}}
Part 2: Select Techniques#
Based on objective, select 2-3 complementary techniques:
For problem exploration:
- 5 Whys - Dig into root causes
- Starbursting - Ask who/what/where/when/why/how
- Six Thinking Hats - Multiple perspectives
For solution generation:
- SCAMPER - Creative variations
- Mind Mapping - Visual organization
- Brainwriting - Silent idea generation
For risk analysis:
- Reverse Brainstorming - What would make this fail?
- Six Thinking Hats (Black Hat) - Critical thinking
- SWOT - Strengths/Weaknesses/Opportunities/Threats
For strategic planning:
- SWOT Analysis - Comprehensive assessment
- Mind Mapping - Strategy visualization
- Starbursting - Question all assumptions
Inform user:
"I'll use these techniques:
- {{technique_1}} - {{reason}}
- {{technique_2}} - {{reason}}
- {{technique_3}} - {{reason}}"
Part 3: Execute Technique 1#
Apply first technique systematically.
5 Whys
Ask "Why?" 5 times to find root cause:
Problem: {{objective}}
Why 1: {{answer}}
Why 2: {{answer}}
Why 3: {{answer}}
Why 4: {{answer}}
Why 5: {{answer}}
Root Cause: {{root_cause}}SCAMPER
Apply each transformation:
Substitute: What can we replace?
Combine: What can we merge?
Adapt: What can we adjust?
Modify: What can we change?
Put to other uses: What else can this do?
Eliminate: What can we remove?
Reverse: What if we did the opposite?Mind Mapping
Create hierarchical idea structure:
Central Topic: {{objective}}
Branch 1: {{category}}
- Sub-idea 1
- Sub-idea 2
Branch 2: {{category}}
- Sub-idea 1
- Sub-idea 2Reverse Brainstorming
Ask: "How could we make this fail?"
Ways to guarantee failure:
1. {{anti-solution_1}}
2. {{anti-solution_2}}
Insights (inverse):
1. {{actual_solution_1}}
2. {{actual_solution_2}}Six Thinking Hats
Examine from 6 perspectives:
White Hat (Facts): {{facts}}
Red Hat (Emotions): {{feelings}}
Black Hat (Caution): {{risks}}
Yellow Hat (Benefits): {{positives}}
Green Hat (Creativity): {{creative_ideas}}
Blue Hat (Process): {{next_steps}}Starbursting
Ask 6 question types:
Who: {{who_questions}}
What: {{what_questions}}
Where: {{where_questions}}
When: {{when_questions}}
Why: {{why_questions}}
How: {{how_questions}}Brainwriting
Silent idea generation:
Round 1 (5 min): Generate {{count}} ideas
Round 2 (5 min): Build on Round 1, add {{count}} more
Round 3 (5 min): Combine and refineSWOT Analysis
Strengths: {{internal_positives}}
Weaknesses: {{internal_negatives}}
Opportunities: {{external_positives}}
Threats: {{external_negatives}}Document all ideas generated.
Part 4: Execute Technique 2#
Apply second technique.
Use same systematic approach as Part 3. Cross-reference ideas from first technique.
Part 5: Execute Technique 3#
Apply third technique.
Use same systematic approach. Look for patterns across all three techniques.
Part 6: Organize Ideas#
Consolidate ideas from all techniques.
Group by category:
## Category 1: {{category_name}}
- Idea 1: {{description}}
- Idea 2: {{description}}
- Idea 3: {{description}}
## Category 2: {{category_name}}
- Idea 1: {{description}}
- Idea 2: {{description}}
[Additional categories...]Remove duplicates - Merge similar ideas
Count total ideas - Report to user
Part 7: Extract Insights#
Analyze all ideas to identify top insights.
Criteria for insights:
- High impact potential
- Feasible given constraints
- Novel or unexpected
- Addresses core objective
- Supported by multiple techniques
Format:
## Key Insights
### Insight 1: {{title}}
**Description:** {{explanation}}
**Source:** {{which_techniques_surfaced_this}}
**Impact:** High | Medium | Low
**Effort:** High | Medium | Low
**Why it matters:** {{rationale}}
### Insight 2: {{title}}
[Same structure]
### Insight 3: {{title}}
[Same structure]Typical count: 3-7 key insights
Part 8: Generate Output Document#
Create brainstorming document per helpers.md#Apply-Variables-to-Template
Use template: brainstorming-session.md (or generate inline if template doesn't exist)
Document structure:
# Brainstorming Session: {{objective}}
**Date:** {{date}}
**Objective:** {{objective}}
**Context:** {{context}}
## Techniques Used
1. {{technique_1}}
2. {{technique_2}}
3. {{technique_3}}
## Ideas Generated
### Category 1: {{category}}
{{ideas}}
### Category 2: {{category}}
{{ideas}}
[All categories...]
## Key Insights
{{insights_from_part_7}}
## Statistics
- Total ideas: {{count}}
- Categories: {{count}}
- Key insights: {{count}}
- Techniques applied: 3
## Recommended Next Steps
{{next_steps}}
---
*Generated by BMAD Method v6 - Creative Intelligence*
*Session duration: {{duration}} minutes*Save to: {{output_folder}}/brainstorming-{{topic}}-{{date}}.md
Inform user:
✓ Brainstorming Complete!
Ideas Generated: {{count}}
Categories: {{count}}
Key Insights: {{count}}
Document: {{file_path}}
Top 3 Insights:
1. {{insight_1_title}}
2. {{insight_2_title}}
3. {{insight_3_title}}Update Status#
Per helpers.md#Update-Workflow-Status
Update bmm-workflow-status.yaml:
last_workflow: brainstorm
last_workflow_date: {{current_date}}
brainstorming:
sessions_completed: {{increment_count}}
last_session_topic: {{objective}}
ideas_generated: {{total_count}}Recommend Next Steps#
Based on objective, recommend logical next workflow:
If brainstorming was for:
Feature ideas → Product Manager
Next: Review and prioritize ideas
Run: /prd or /tech-spec
Use brainstorming insights to inform requirementsProblem solutions → System Architect
Next: Evaluate solutions against architecture
Run: /architecture
Test top solutions for NFR complianceRisk identification → Scrum Master
Next: Incorporate risks into sprint planning
Run: /sprint-planning
Add mitigation stories for identified risksResearch questions → Creative Intelligence
Next: Conduct research on top insights
Run: /research
Validate assumptions with dataProcess improvements → Business Analyst or Scrum Master
Next: Document improved process
Create process documentation
Test with teamHelper References#
- Load config:
helpers.md#Combined-Config-Load - Apply template:
helpers.md#Apply-Variables-to-Template - Save document:
helpers.md#Save-Output-Document - Update status:
helpers.md#Update-Workflow-Status - Determine next:
helpers.md#Determine-Next-Workflow
Notes for LLMs#
- Use TodoWrite to track 8 brainstorming steps
- Apply all selected techniques thoroughly - no shortcuts
- Document EVERY idea, even seemingly weak ones
- Look for patterns across techniques
- Quantify results (idea counts, categories, etc.)
- Extract actionable insights, not just raw ideas
- Recommend specific next workflow based on objective
- Use structured frameworks - avoid free-form thinking
- Cross-reference ideas from different techniques
- Focus on quality insights over quantity of ideas
- Keep session focused on stated objective
- Use helpers.md references for all common operations
Remember: Structured brainstorming using multiple techniques generates more comprehensive and creative results than single-method approaches. Document everything, extract insights, and provide clear next steps.