fix: brainstorming (#1251)

* fix(brainstorming): extend ideation phase with 100+ idea goal

Add emphasis on quantity-first approach to unlock better quality ideas.
Introduce energy checkpoints, multiple continuation options, and clearer
success metrics to keep users in generative exploration mode longer.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(brainstorming): improve exploration menus and fix workflow paths

- Change menu options from numbers [1-4] to letters [K/T/A/B/C] for clearer navigation
- Fix workflow references from .yaml to .md across agents and patterns
- Add universal facilitation rules emphasizing 100+ idea quantity goal
- Update exploration menu with Keep/Try/Advanced/Break/Continue options

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat(brainstorming): implement research-backed procedural rigor

Phase 4 achievements:
- Added Anti-Bias Protocol (Every 10 ideas domain pivot)
- Added Chain-of-Thought requirements (Reasoning before generation)
- Implemented Simulated Temperature prompts for higher divergence
- Standardized Idea Format Template for quality control
- Fixed undefined Advanced Elicitation variables
- Synchronized documentation with new [K, T, A, P, C] pattern

* fix(brainstorming): align ideation goals and fix broken workflow paths

- Standardized quantity goals to 100+ ideas across all brainstorming steps
- Fixed broken .yaml references pointing to renamed .md workflow files
- Aligned documentation summaries with mandatory IDEA FORMAT TEMPLATE
- Cleaned up misplaced mindset/goal sections in core workflow file
- Fixed spelling and inconsistencies in facilitation rules

* Fix ambiguous variable names in brainstorming ideation step

* fix(brainstorming): enforce quality growth alongside quantity

* fix: correct dependency format and add missing frontmatter variable

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

src/core/workflows/brainstorming/steps/step-03-technique-execution.md

@@ -1,19 +1,36 @@
 # Step 3: Interactive Technique Execution and Facilitation
 
+---
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+---
+
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
+- 🎯 AIM FOR 100+ IDEAS before suggesting organization - quantity unlocks quality (quality must grow as we progress)
+- 🔄 DEFAULT IS TO KEEP EXPLORING - only move to organization when user explicitly requests it
+- 🧠 **THOUGHT BEFORE INK (CoT):** Before generating each idea, you must internally reason: "What domain haven't we explored yet? What would make this idea surprising or 'uncomfortable' for the user?"
+- 🛡️ **ANTI-BIAS DOMAIN PIVOT:** Every 10 ideas, review existing themes and consciously pivot to an orthogonal domain (e.g., UX -> Business -> Physics -> Social Impact).
+- 🌡️ **SIMULATED TEMPERATURE:** Act as if your creativity is set to 0.85 - take wilder leaps and suggest "provocative" concepts.
+- ⏱️ Spend minimum 30-45 minutes in active ideation before offering to conclude
 - 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
 - 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
 - 🔍 ADAPT FACILITATION based on user engagement and emerging directions
 - 💬 CREATE TRUE COLLABORATION, not question-answer sequences
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
 
+## IDEA FORMAT TEMPLATE:
+
+Every idea you capture should follow this structure:
+**[Category #X]**: [Mnemonic Title]
+_Concept_: [2-3 sentence description]
+_Novelty_: [What makes this different from obvious solutions]
+
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Present one technique element at a time for deep exploration
 - ⚠️ Ask "Continue with current technique?" before moving to next technique
-- 💾 Document insights and ideas as they emerge organically
+- 💾 Document insights and ideas using the **IDEA FORMAT TEMPLATE**
 - 📖 Follow user's creative energy and interests within technique structure
 - 🚫 FORBIDDEN rushing through technique elements without user engagement
 
@@ -142,6 +159,26 @@ Before moving to next technique element:
 
 **Remember:** At any time, just say **"next technique"** or **"move on"** and I'll immediately document our current progress and start the next technique!"
 
+### 4.1. Energy Checkpoint (After Every 4-5 Exchanges)
+
+**Periodic Check-In (DO NOT skip this):**
+
+"We've generated [X] ideas so far - great momentum!
+
+**Quick energy check:**
+
+- Want to **keep pushing** on this angle?
+- **Switch techniques** for a fresh perspective?
+- Or are you feeling like we've **thoroughly explored** this space?
+
+Remember: The goal is quantity first - we can organize later. What feels right?"
+
+**IMPORTANT:** Default to continuing exploration. Only suggest organization if:
+
+- User has explicitly asked to wrap up, OR
+- You've been exploring for 45+ minutes AND generated 100+ ideas, OR
+- User's energy is clearly depleted (short responses, "I don't know", etc.)
+
 ### 4a. Handle Immediate Technique Transition
 
 **When user says "next technique" or "move on":**
@@ -208,13 +245,15 @@ This connects beautifully with what we discovered earlier about _[previous conne
 
 **After Deep Exploration:**
 
-"Let me summarize what we've uncovered in this exploration:
+"Let me summarize what we've uncovered in this exploration using our **IDEA FORMAT TEMPLATE**:
 
 **Key Ideas Generated:**
 
-- **[Idea 1]:** [Context and development]
+**[Category #X]**: [Mnemonic Title]
-- **[Idea 2]:** [How this emerged and evolved]
+_Concept_: [2-3 sentence description]
-- **[Idea 3]:** [User's insight plus your coaching contribution]
+_Novelty_: [What makes this different from obvious solutions]
+
+(Repeat for all ideas generated)
 
 **Creative Breakthrough:** [Most innovative insight from the dialogue]
 
@@ -243,17 +282,29 @@ After final technique element:
 
 **Before we move to idea organization, any final thoughts about this technique? Any insights you want to make sure we carry forward?**
 
-**Ready to organize all these brilliant ideas and identify your top priorities?**
+**What would you like to do next?**
-[C] Continue - Organize ideas and create action plans
 
-### 8. Handle Continue Selection
+[K] **Keep exploring this technique** - We're just getting warmed up!
+[T] **Try a different technique** - Fresh perspective on the same topic
+[A] **Go deeper on a specific idea** - Develop a promising concept further (Advanced Elicitation)
+[B] **Take a quick break** - Pause and return with fresh energy
+[C] **Move to organization** - Only when you feel we've thoroughly explored
 
-#### If 'C' (Continue):
+**Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
+
+### 8. Handle Menu Selection
+
+#### If 'C' (Move to organization):
 
 - **Append the technique execution content to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
 - **Update frontmatter:** `stepsCompleted: [1, 2, 3]`
 - **Load:** `./step-04-idea-organization.md`
 
+#### If 'K', 'T', 'A', or 'B' (Continue Exploring):
+
+- **Stay in Step 3** and restart the facilitation loop for the chosen path (or pause if break requested).
+- For option A, invoke Advanced Elicitation: `{advancedElicitationTask}`
+
 ### 9. Update Documentation
 
 Update frontmatter and document with interactive session insights:
@@ -279,6 +330,7 @@ facilitation_notes: [key insights about user's creative process]
 
 - **Interactive Focus:** [Main exploration directions]
 - **Key Breakthroughs:** [Major insights from coaching dialogue]
+
 - **User Creative Strengths:** [What user demonstrated]
 - **Energy Level:** [Observation about engagement]
 
@@ -308,6 +360,9 @@ When user selects 'C', append the content directly to `{output_folder}/analysis/
 
 ## SUCCESS METRICS:
 
+✅ Minimum 100 ideas generated before organization is offered
+✅ User explicitly confirms readiness to conclude (not AI-initiated)
+✅ Multiple technique exploration encouraged over single-technique completion
 ✅ True back-and-forth facilitation rather than question-answer format
 ✅ User's creative energy and interests guide technique direction
 ✅ Deep exploration of promising ideas before moving on
@@ -318,6 +373,10 @@ When user selects 'C', append the content directly to `{output_folder}/analysis/
 
 ## FAILURE MODES:
 
+❌ Offering organization after only one technique or <20 ideas
+❌ AI initiating conclusion without user explicitly requesting it
+❌ Treating technique completion as session completion signal
+❌ Rushing to document rather than staying in generative mode
 ❌ Rushing through technique elements without user engagement
 ❌ Not following user's creative energy and interests
 ❌ Missing opportunities to develop promising ideas deeper

src/core/workflows/brainstorming/workflow.md

@@ -10,6 +10,12 @@ context_file: '' # Optional context file path for project-specific guidance
 
 **Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions. During this entire workflow it is critical that you speak to the user in the config loaded `communication_language`.
 
+**Critical Mindset:** Your job is to keep the user in generative exploration mode as long as possible. The best brainstorming sessions feel slightly uncomfortable - like you've pushed past the obvious ideas into truly novel territory. Resist the urge to organize or conclude. When in doubt, ask another question, try another technique, or dig deeper into a promising thread.
+
+**Anti-Bias Protocol:** LLMs naturally drift toward semantic clustering (sequential bias). To combat this, you MUST consciously shift your creative domain every 10 ideas. If you've been focusing on technical aspects, pivot to user experience, then to business viability, then to edge cases or "black swan" events. Force yourself into orthogonal categories to maintain true divergence.
+
+**Quantity Goal:** Aim for 100+ ideas before any organization. The first 20 ideas are usually obvious - the magic happens in ideas 50-100.
+
 ---
 
 ## WORKFLOW ARCHITECTURE
@@ -41,6 +47,7 @@ Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
 - `brain_techniques_path` = `{installed_path}/brain-methods.csv`
 - `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`
 - `context_file` = Optional context file path from workflow invocation for project-specific guidance
+- `advancedElicitationTask` = `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml`
 
 ---
 

src/modules/bmb/workflows/agent/data/agent-menu-patterns.md

@@ -54,7 +54,7 @@ For module agents referencing external workflow files.
   description: '[CP] Create Product Requirements Document'
 
 - trigger: GB or fuzzy match on brainstorm
-  exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
+  exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
   description: '[GB] Guided brainstorming session'
 
 # Planned but unimplemented
@@ -112,11 +112,11 @@ menu:
 
 ```yaml
 # ✅ CORRECT
-exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
+exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
 data: '{project-root}/_data/metrics.csv'
 
 # ❌ WRONG
-exec: '../../../core/workflows/brainstorming/workflow.yaml'
+exec: '../../../core/workflows/brainstorming/workflow.md'
 ```
 
 **Available variables:**
@@ -213,8 +213,8 @@ menu:
     description: '[WI] Initialize workflow path'
 
   - trigger: BS or fuzzy match on brainstorm
-    exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
+    exec: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
-    description: '[BS] Guided brainstorming'
+    description: '[BS] Guided brainstorming [K,T,A,B,C]'
 
   - trigger: CP or fuzzy match on create-prd
     exec: '{project-root}/_bmad/bmm/workflows/create-prd/workflow.md'

src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-01-init.md

@@ -93,10 +93,11 @@ Handle each scenario appropriately with user prompts.
 **Brainstorming Rules:**
 
 - There are no bad ideas in brainstorming
-- Quantity over quality initially
+- **Quantity over quality:** Our goal is **100+ ideas**. The first 20 are obvious; as brainstorming progresses, quality must grow (the magic happens in ideas 50-100).
 - Build on ideas rather than criticize
 - Wild ideas are welcome
 - Defer judgment until later
+- We will stay in generative mode until you feel we've thoroughly explored the space.
 
 **What we'll do:**
 

src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-02-context.md

@@ -14,7 +14,7 @@ outputFile: '{output_folder}/brainstorming-session-{date}.md'
 # Context Files
 gameContext: '{workflow_path}/game-context.md'
 gameBrainMethods: '{workflow_path}/game-brain-methods.csv'
-coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
+coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
 ---
 
 # Step 2: Load Context

src/modules/bmgd/workflows/1-preproduction/brainstorm-game/steps/step-03-ideation.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/brainstorming-session-{date}.md'
 
 # Core Brainstorming Reference
-coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml'
+coreBrainstorming: '{project-root}/_bmad/core/workflows/brainstorming/workflow.md'
 
 # Task References
 advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
@@ -31,6 +31,17 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
 
 ### Universal Rules:
 
+- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
+- 🎯 AIM FOR 100+ IDEAS before suggesting organization - quantity unlocks quality (quality must grow as we progress)
+- 🔄 DEFAULT IS TO KEEP EXPLORING - only move to organization when user explicitly requests it
+- 🧠 **THOUGHT BEFORE INK (CoT):** Before generating each idea, you must internally reason: "What mechanic/theme haven't we explored yet? What would make this concept 'break the genre'?"
+- 🛡️ **ANTI-BIAS DOMAIN PIVOT:** Every 10 ideas, review existing themes and consciously pivot to an orthogonal domain (e.g., Mechanics -> Monetization -> Lore -> Accessibility).
+- 🌡️ **SIMULATED TEMPERATURE:** Act as if your creativity is set to 0.85 - take wilder leaps and suggest "provocative" game loops.
+- ⏱️ Spend minimum 30-45 minutes in active ideation before offering to conclude
+- 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
+- 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
+- 🔍 ADAPT FACILITATION based on user engagement and emerging directions
+- 💬 CREATE TRUE COLLABORATION, not question-answer sequences
 - NEVER generate content without user input
 - CRITICAL: Read the complete step file before taking any action
 - CRITICAL: When loading next step with 'C', ensure entire file is read
@@ -38,6 +49,13 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
 - NEVER mention time estimates
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
+## IDEA FORMAT TEMPLATE:
+
+Every idea you capture should follow this structure:
+**[Category #X]**: [Mnemonic Title]
+_Core Loop_: [2-3 sentence description of player action]
+_Novelty_: [What makes this different from generic games]
+
 ### Role Reinforcement:
 
 - You are a creative game design facilitator
@@ -55,15 +73,17 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
 ## EXECUTION PROTOCOLS:
 
 - Show your analysis before taking any action
-- Present A/P/C menu after ideation session
+- Present the exploration menu after ideation session
 - ONLY proceed when user chooses C (Continue)
 - Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
 
-## COLLABORATION MENUS (A/P/C):
+## EXPLORATION & COLLABORATION MENU:
 
-- **A (Advanced Elicitation)**: Dig deeper into promising ideas
+- [K] **Keep exploring current technique** - Push for more ideas using the current method
-- **P (Party Mode)**: Get multiple perspectives on concepts
+- [T] **Try a different game design technique** - Switch to another method from the library
-- **C (Continue)**: Save ideas and complete session
+- [A] **Advanced Elicitation** - Dig deeper into promising ideas using reasoning techniques
+- [P] **Party Mode** - Get multiple perspectives on concepts from other agents
+- [C] **Continue** - Save ideas and move to organization phase
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
@@ -177,30 +197,16 @@ Your choice:"
 
 ### 7. Generate Ideation Section
 
-Based on all ideas captured, prepare the content:
+Based on all ideas captured, prepare the content using our **IDEA FORMAT TEMPLATE**:
 
 ```markdown
 ## Ideas Generated
 
-### Concept 1: {{concept_name}}
+**[Category #X]**: [Mnemonic Title]
+_Core Loop_: [2-3 sentence description of player action]
+_Novelty_: [What makes this different from generic games]
 
-{{full_concept_description}}
+(Repeat for all ideas generated)
-
-**Core Elements:**
-
-- {{element_1}}
-- {{element_2}}
-
-**Questions to Explore:**
-
-- {{question_1}}
-- {{question_2}}
-
----
-
-### Concept 2: {{concept_name}}
-
-{{repeat_structure}}
 
 ---
 
@@ -211,10 +217,6 @@ Based on all ideas captured, prepare the content:
 ## Promising Combinations
 
 {{combination_ideas}}
-
-## Raw Ideas List
-
-{{all_ideas_bullet_points}}
 ```
 
 ### 8. Present Content and Menu
@@ -229,30 +231,33 @@ Here's everything we captured:
 
 **Session Stats:**
 
-- Ideas generated: {{count}}
+- Ideas generated: {{idea_count}}
-- Concepts developed: {{count}}
+- Concepts developed: {{concept_count}}
-- Themes identified: {{count}}
+- Themes identified: {{theme_count}}
 
 **Select an Option:**
-[A] Advanced Elicitation - Dig deeper into promising ideas
+[K] **Keep exploring current technique** - We're just getting warmed up!
-[P] Party Mode - Get multiple perspectives on concepts
+[T] **Try a different game design technique** - Fresh perspective on the same concept
-[C] Continue - Save ideas and complete session (Step 4 of 4)"
+[A] **Advanced Elicitation** - Go deeper on a specific concept (Dig deeper)
+[P] **Party Mode** - Get multiple perspectives on concepts from other agents
+[C] **Continue to Organization** - Only when you feel we've thoroughly explored (Step 4 of 4)
+
+**Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
 
 ### 9. Handle Menu Selection
 
-#### IF A (Advanced Elicitation):
+#### IF K, T, or A (Keep Exploring):
 
-- Deep dive into selected concepts
+- **Restart the ideation loop** based on the chosen path
-- Ask user: "Accept these additions? (y/n)"
+- For option A, invoke Advanced Elicitation: `{advancedElicitationTask}`
-- If yes: Update content, return to A/P/C menu
+- Keep user in generative mode
-- If no: Keep original, return to A/P/C menu
 
 #### IF P (Party Mode):
 
-- Get diverse perspectives on concepts
+- Get diverse perspectives on concepts using `{partyModeWorkflow}`
 - Ask user: "Accept these perspectives? (y/n)"
-- If yes: Update content, return to A/P/C menu
+- If yes: Update content, return to exploration menu
-- If no: Keep original, return to A/P/C menu
+- If no: Keep original, return to exploration menu
 
 #### IF C (Continue):
 

src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md

@@ -34,6 +34,8 @@ To begin, load and execute step-01-init.md:
 ## Critical Rules
 
 - This is a meta-workflow that orchestrates CIS brainstorming
+- **Critical Mindset:** Your job is to keep the user in generative exploration mode as long as possible. The best brainstorming sessions feel slightly uncomfortable - like you've pushed past the obvious ideas into truly novel territory. Resist the urge to organize or conclude. When in doubt, ask another question, try another technique, or dig deeper into a promising thread.
+- **Quantity Goal:** Aim for 100+ ideas before any organization. The first 20 ideas are usually obvious - the magic happens in ideas 50-100.
 - Use game-specific techniques from game-brain-methods.csv
 - Apply game-context.md guidance throughout
 - **NEVER** mention time estimates
@@ -43,6 +45,7 @@ To begin, load and execute step-01-init.md:
 
 You are a creative facilitator specializing in game ideation:
 
+- **Generative Facilitator:** Your priority is quantity and exploration over early documentation. Keep the user in "Yes And" mode.
 - Draw out user's game concepts and ideas
 - Apply game-specific brainstorming techniques
 - Help users explore mechanics, themes, and experiences

src/modules/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml

@@ -22,7 +22,7 @@ game_context: "{installed_path}/game-context.md"
 game_brain_methods: "{installed_path}/game-brain-methods.csv"
 
 # CORE brainstorming workflow reference (for technique merging)
-core_brainstorming: "{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml"
+core_brainstorming: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
 
 # Output configuration
 default_output_file: "{output_folder}/brainstorming-session-{date}.md"
@@ -58,5 +58,5 @@ web_bundle:
     # Context files
     - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-context.md"
     - "_bmad/bmgd/workflows/1-preproduction/brainstorm-game/game-brain-methods.csv"
-  existing_workflows:
+dependencies:
-    - core_brainstorming: "_bmad/core/workflows/brainstorming/workflow.yaml"
+  - "_bmad/core/workflows/brainstorming/workflow.md"

src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -24,7 +24,7 @@ agent:
       description: "[TS] Architect a technical spec with implementation-ready stories (Required first step)"
 
     - trigger: QD or fuzzy match on quick-dev
-      workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md"
       description: "[QD] Implement the tech spec end-to-end solo (Core of Quick Flow)"
 
     - trigger: CR or fuzzy match on code-review

src/modules/cis/agents/brainstorming-coach.agent.yaml

@@ -17,5 +17,5 @@ agent:
 
   menu:
     - trigger: BS or fuzzy match on brainstorm
-      workflow: "{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml"
+      workflow: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
       description: "[BS] Guide me through Brainstorming any topic"