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>
This commit is contained in:
Davor Racić 2026-01-05 00:12:03 +01:00
parent da889c9da4
commit 33e78d025a
7 changed files with 47 additions and 30 deletions

View File

@ -266,15 +266,15 @@ After final technique element:
**What would you like to do next?** **What would you like to do next?**
[1] **Keep exploring this technique** - We're just getting warmed up! [K] **Keep exploring this technique** - We're just getting warmed up!
[2] **Try a different technique** - Fresh perspective on the same topic [T] **Try a different technique** - Fresh perspective on the same topic
[3] **Go deeper on a specific idea** - Develop a promising concept further [A] **Go deeper on a specific idea** - Develop a promising concept further (Advanced Elicitation)
[4] **Take a quick break** - Pause and return with fresh energy [B] **Take a quick break** - Pause and return with fresh energy
[C] **Move to organization** - Only when you feel we've thoroughly explored (Type 'C' to continue) [C] **Move to organization** - Only when you feel we've thoroughly explored
**Default recommendation:** Unless you feel we've generated at least 50+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted. **Default recommendation:** Unless you feel we've generated at least 50+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
### 8. Handle Continue Selection ### 8. Handle Menu Selection
#### If 'C' (Move to organization): #### If 'C' (Move to organization):
@ -282,7 +282,7 @@ After final technique element:
- **Update frontmatter:** `stepsCompleted: [1, 2, 3]` - **Update frontmatter:** `stepsCompleted: [1, 2, 3]`
- **Load:** `./step-04-idea-organization.md` - **Load:** `./step-04-idea-organization.md`
#### If '1', '2', '3', or '4' (Continue Exploring): #### 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). - **Stay in Step 3** and restart the facilitation loop for the chosen path (or pause if break requested).
### 9. Update Documentation ### 9. Update Documentation

View File

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

View File

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

View File

@ -31,6 +31,14 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
### Universal Rules: ### Universal Rules:
- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
- 🎯 AIM FOR 100+ IDEAS before suggesting organization - quantity unlocks quality
- 🔄 DEFAULT IS TO KEEP EXPLORING - only move to organization when user explicitly requests it
- ⏱️ 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 - NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action - CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read - CRITICAL: When loading next step with 'C', ensure entire file is read
@ -55,15 +63,17 @@ Facilitate the actual brainstorming session using selected techniques. Capture a
## EXECUTION PROTOCOLS: ## EXECUTION PROTOCOLS:
- Show your analysis before taking any action - 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) - ONLY proceed when user chooses C (Continue)
- Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step - 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) ## Sequence of Instructions (Do not deviate, skip, or optimize)
@ -234,25 +244,28 @@ Here's everything we captured:
- Themes identified: {{count}} - Themes identified: {{count}}
**Select an Option:** **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 50+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
### 9. Handle Menu Selection ### 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): #### IF P (Party Mode):
- Get diverse perspectives on concepts - Get diverse perspectives on concepts using `{partyModeWorkflow}`
- Ask user: "Accept these perspectives? (y/n)" - 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): #### IF C (Continue):

View File

@ -34,6 +34,8 @@ To begin, load and execute step-01-init.md:
## Critical Rules ## Critical Rules
- This is a meta-workflow that orchestrates CIS brainstorming - 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 - Use game-specific techniques from game-brain-methods.csv
- Apply game-context.md guidance throughout - Apply game-context.md guidance throughout
- **NEVER** mention time estimates - **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: 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 - Draw out user's game concepts and ideas
- Apply game-specific brainstorming techniques - Apply game-specific brainstorming techniques
- Help users explore mechanics, themes, and experiences - Help users explore mechanics, themes, and experiences

View File

@ -24,7 +24,7 @@ agent:
description: "[TS] Architect a technical spec with implementation-ready stories (Required first step)" description: "[TS] Architect a technical spec with implementation-ready stories (Required first step)"
- trigger: QD or fuzzy match on quick-dev - 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)" description: "[QD] Implement the tech spec end-to-end solo (Core of Quick Flow)"
- trigger: CR or fuzzy match on code-review - trigger: CR or fuzzy match on code-review

View File

@ -17,5 +17,5 @@ agent:
menu: menu:
- trigger: BS or fuzzy match on brainstorm - 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" description: "[BS] Guide me through Brainstorming any topic"