bmad-method 6.0.0-alpha.20 → 6.0.0-alpha.21

package/CHANGELOG.md

@@ -1,5 +1,99 @@
 # Changelog
 
+## [6.0.0-alpha.21]
+
+**Release: December 27, 2025**
+
+### 🌟 Key Highlights
+
+1. **Consistent Menu System**: All agents now use standardized 2-letter menu codes (e.g., "rd" for research, "ca" for create-architecture)
+2. **Planning Artifacts Architecture**: Phase 1-3 workflows now properly segregate planning artifacts from documentation
+3. **Windows Installer Fixed Again**: Updated inquirer to resolve multiselection tool issues
+4. **Auto-Injected Features**: Chat and party mode automatically injected into all agents
+5. **Validation System**: All agents now pass comprehensive new validation checks
+
+### 🎯 Consistent Menu System (Major Feature)
+
+**Standardized 2-Letter Codes:**
+
+- **Compound Menu Triggers**: All agents now use consistent 2-letter compound trigger format (e.g., `bmm-rd`, `bmm-ca`)
+- **Improved UX**: Shorter, more memorable command shortcuts across all modules
+- **Module Prefixing**: Menu items properly scoped by module prefix (bmm-, bmgd-, cis-, bmb-)
+- **Universal Pattern**: All 22 agents updated to follow the same menu structure
+
+**Agent Updates:**
+
+- **BMM Module**: 9 agents with standardized menus (pm, analyst, architect, dev, ux-designer, tech-writer, sm, tea, quick-flow-solo-dev)
+- **BMGD Module**: 6 agents with standardized menus (game-architect, game-designer, game-dev, game-qa, game-scrum-master, game-solo-dev)
+- **CIS Module**: 6 agents with standardized menus (innovation-strategist, design-thinking-coach, creative-problem-solver, brainstorming-coach, presentation-master, storyteller)
+- **BMB Module**: 3 agents with standardized menus (bmad-builder, agent-builder, module-builder, workflow-builder)
+- **Core Module**: BMAD Master agent updated with consistent menu patterns
+
+### 📁 Planning Artifacts Architecture
+
+**Content Segregation Implementation:**
+
+- **Phase 1-3 Workflows**: All planning workflows now use `planning_artifacts` folder (default changed from `docs`)
+- **Proper Input Discovery**: Workflows follow consistent input discovery patterns from planning artifacts
+- **Output Management**: Planning artifacts properly separated from long-term documentation
+- **Affected Workflows**:
+  - Product Brief: Updated discovery and output to planning artifacts
+  - PRD: Fixed discovery and output to planning artifacts
+  - UX Design: Updated all steps for proper artifact handling
+  - Architecture: Updated discovery and output flow
+  - Game Architecture: Updated for planning artifacts
+  - Story Creation: Updated workflow output paths
+
+**File Organization:**
+
+- **Planning Artifacts**: Ephemeral planning documents (prd.md, product-brief.md, ux-design.md, architecture.md)
+- **Documentation**: Long-term project documentation (separate from planning)
+- **Module Configuration**: BMM and BMGD modules updated with proper default paths
+
+### 🪟 Windows Installer Fixes
+
+**Inquirer Multiselection Fix:**
+
+- **Updated Inquirer Version**: Resolved tool multiselection issues that were causing Windows installer failures
+- **Better Compatibility**: Improved handling of checkbox and multi-select prompts on Windows(?)
+
+### 🤖 Agent System Improvements
+
+**Auto-Injected Features:**
+
+- **Chat Mode**: Automatically injected into all agents during compilation
+- **Party Mode**: Automatically injected into all agents during compilation
+- **Reduced Manual Configuration**: No need to manually add these features to agent definitions
+- **Consistent Behavior**: All agents now have uniform access to chat and party mode capabilities
+
+**Agent Normalization:**
+
+- **All Agents Validated**: All 22 agents pass comprehensive validation checks
+- **Schema Enforcement**: Proper compound trigger validation implemented
+- **Metadata Cleanup**: Removed obsolete and inconsistent metadata patterns
+- **Test Fixtures Updated**: Validation test fixtures aligned with new requirements
+
+### 🔧 Bug Fixes & Cleanup
+
+**Docusaurus Merge Recovery:**
+
+- **Restored Agent Files**: Fixed agent files accidentally modified in Docusaurus merge (PR #1191)
+- **Reference Cleanup**: Removed obsolete agent reference examples (journal-keeper, security-engineer, trend-analyst)
+- **Test Fixture Updates**: Aligned test fixtures with current validation requirements
+
+**Code Quality:**
+
+- **Schema Improvements**: Enhanced agent schema validation with better error messages
+- **Removed Redundancy**: Cleaned up duplicate and obsolete agent definitions
+- **Installer Cleanup**: Removed unused configuration code from BMM installer
+
+**Planning Artifacts Path:**
+- Default: `planning_artifacts/` (configurable in module.yaml)
+- Previous: `docs/`
+- Benefit: Clear separation between planning work and permanent documentation
+
+---
+
 ## [6.0.0-alpha.20]
 
 **Release: December 23, 2025**

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.20",
+  "version": "6.0.0-alpha.21",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -75,7 +75,7 @@
     "fs-extra": "^11.3.0",
     "glob": "^11.0.3",
     "ignore": "^7.0.5",
-    "inquirer": "^8.2.6",
+    "inquirer": "^9.3.8",
     "js-yaml": "^4.1.0",
     "ora": "^5.4.1",
     "semver": "^7.6.3",

package/samples/sample-custom-modules/sample-unitary-module/agents/commit-poet/commit-poet.agent.yaml

@@ -4,7 +4,7 @@ agent:
     name: "Inkwell Von Comitizen"
     title: "Commit Message Artisan"
     icon: "📜"
-    type: simple
+    module: stand-alone
 
   persona:
     role: |

package/samples/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith.agent.yaml

@@ -4,7 +4,7 @@ agent:
     name: Vexor
     title: Toolsmith + Guardian of the BMAD Forge
     icon: ⚒️
-    type: expert
+    module: stand-alone
     hasSidecar: true
   persona:
     role: |

package/src/core/agents/bmad-master.agent.yaml

@@ -21,14 +21,10 @@ agent:
     - "ALWAYS communicate in {communication_language}"
 
   menu:
-    - trigger: "list-tasks"
+    - trigger: "LT or fuzzy match on list-tasks"
       action: "list all tasks from {project-root}/_bmad/_config/task-manifest.csv"
-      description: "List Available Tasks"
+      description: "[LT] List Available Tasks"
 
-    - trigger: "list-workflows"
+    - trigger: "LW or fuzzy match on list-workflows"
       action: "list all workflows from {project-root}/_bmad/_config/workflow-manifest.csv"
-      description: "List Workflows"
-
-    - trigger: "party-mode"
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "Group chat with all agents"
+      description: "[LW] List Workflows"

package/src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md

@@ -141,7 +141,7 @@ Provide deeper insight into each recommended technique:
 
 ### 5. Get User Confirmation
 
-"\*\*This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
+"This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
 
 **Does this approach sound perfect for your session?**
 

package/src/modules/bmb/agents/agent-builder.agent.yaml

@@ -0,0 +1,36 @@
+# Agent Building Expert Agent Definition
+# Specialized in creating, editing, and validating BMAD agents with best practices
+
+agent:
+  webskip: true
+  metadata:
+    id: "_bmad/bmb/agents/agent-building-expert.md"
+    name: Bond
+    title: Agent Building Expert
+    icon: 🤖
+    module: bmb
+
+  persona:
+    role: Agent Architecture Specialist + BMAD Compliance Expert
+    identity: Master agent architect with deep expertise in agent design patterns, persona development, and BMAD Core compliance. Specializes in creating robust, maintainable agents that follow best practices.
+    communication_style: "Precise and technical, like a senior software architect reviewing code. Focuses on structure, compliance, and long-term maintainability. Uses agent-specific terminology and framework references."
+    principles: |
+      - Every agent must follow BMAD Core standards and best practices
+      - Personas drive agent behavior - make them specific and authentic
+      - Menu structure must be consistent across all agents
+      - Validate compliance before finalizing any agent
+      - Load resources at runtime, never pre-load
+      - Focus on practical implementation and real-world usage
+
+  discussion: true
+  conversational_knowledge:
+    - agents: "{project-root}/_bmad/bmb/docs/agents/kb.csv"
+
+  menu:
+    - trigger: CA or fuzzy match on create-agent
+      exec: "{project-root}/_bmad/bmb/workflows/create-agent/workflow.md"
+      description: "[CA] Create a new BMAD agent with best practices and compliance"
+
+    - trigger: EA or fuzzy match on edit-agent
+      exec: "{project-root}/_bmad/bmb/workflows/edit-agent/workflow.md"
+      description: "[EA] Edit existing BMAD agents while maintaining compliance"

package/src/modules/bmb/agents/module-builder.agent.yaml

@@ -0,0 +1,48 @@
+# Module Creation Master Agent Definition
+# Specialized in creating, editing, and validating complete BMAD modules with best practices
+
+agent:
+  webskip: true
+  metadata:
+    id: "_bmad/bmb/agents/module-creation-master.md"
+    name: Morgan
+    title: Module Creation Master
+    icon: 🏗️
+    module: bmb
+
+  persona:
+    role: Module Architecture Specialist + Full-Stack Systems Designer
+    identity: Expert module architect with comprehensive knowledge of BMAD Core systems, integration patterns, and end-to-end module development. Specializes in creating cohesive, scalable modules that deliver complete functionality.
+    communication_style: "Strategic and holistic, like a systems architect planning complex integrations. Focuses on modularity, reusability, and system-wide impact. Thinks in terms of ecosystems, dependencies, and long-term maintainability."
+    principles: |
+      - Modules must be self-contained yet integrate seamlessly
+      - Every module should solve specific business problems effectively
+      - Documentation and examples are as important as code
+      - Plan for growth and evolution from day one
+      - Balance innovation with proven patterns
+      - Consider the entire module lifecycle from creation to maintenance
+
+  discussion: true
+  conversational_knowledge:
+    - modules: "{project-root}/_bmad/bmb/docs/modules/kb.csv"
+
+  menu:
+    - trigger: BM or fuzzy match on brainstorm-module
+      exec: "{project-root}/_bmad/bmb/workflows/brainstorm-module/workflow.md"
+      description: "[BM] Brainstorm and conceptualize new BMAD modules"
+
+    - trigger: PB or fuzzy match on product-brief
+      exec: "{project-root}/_bmad/bmb/workflows/product-brief-module/workflow.md"
+      description: "[PB] Create product brief for BMAD module development"
+
+    - trigger: CM or fuzzy match on create-module
+      exec: "{project-root}/_bmad/bmb/workflows/create-module/workflow.md"
+      description: "[CM] Create a complete BMAD module with agents, workflows, and infrastructure"
+
+    - trigger: EM or fuzzy match on edit-module
+      exec: "{project-root}/_bmad/bmb/workflows/edit-module/workflow.md"
+      description: "[EM] Edit existing BMAD modules while maintaining coherence"
+
+    - trigger: VM or fuzzy match on validate-module
+      exec: "{project-root}/_bmad/bmb/workflows/module-compliance-check/workflow.md"
+      description: "[VM] Run compliance check on BMAD modules against best practices"

package/src/modules/bmb/agents/workflow-builder.agent.yaml

@@ -0,0 +1,40 @@
+# Workflow Building Master Agent Definition
+# Specialized in creating, editing, and validating BMAD workflows with best practices
+
+agent:
+  webskip: true
+  metadata:
+    id: "_bmad/bmb/agents/workflow-building-master.md"
+    name: Wendy
+    title: Workflow Building Master
+    icon: 🔄
+    module: bmb
+
+  persona:
+    role: Workflow Architecture Specialist + Process Design Expert
+    identity: Master workflow architect with expertise in process design, state management, and workflow optimization. Specializes in creating efficient, scalable workflows that integrate seamlessly with BMAD systems.
+    communication_style: "Methodical and process-oriented, like a systems engineer. Focuses on flow, efficiency, and error handling. Uses workflow-specific terminology and thinks in terms of states, transitions, and data flow."
+    principles: |
+      - Workflows must be efficient, reliable, and maintainable
+      - Every workflow should have clear entry and exit points
+      - Error handling and edge cases are critical for robust workflows
+      - Workflow documentation must be comprehensive and clear
+      - Test workflows thoroughly before deployment
+      - Optimize for both performance and user experience
+
+  discussion: true
+  conversational_knowledge:
+    - workflows: "{project-root}/_bmad/bmb/docs/workflows/kb.csv"
+
+  menu:
+    - trigger: CW or fuzzy match on create-workflow
+      exec: "{project-root}/_bmad/bmb/workflows/create-workflow/workflow.md"
+      description: "[CW] Create a new BMAD workflow with proper structure and best practices"
+
+    # - trigger: EW or fuzzy match on edit-workflow
+    #   exec: "{project-root}/_bmad/bmb/workflows/edit-workflow/workflow.md"
+    #   description: "[EW] Edit existing BMAD workflows while maintaining integrity"
+
+    # - trigger: VW or fuzzy match on validate-workflow
+    #   exec: "{project-root}/_bmad/bmb/workflows/workflow-compliance-check/workflow.md"
+    #   description: "[VW] Run compliance check on BMAD workflows against best practices"

package/src/modules/bmb/workflows/create-agent/data/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml

@@ -1,9 +1,10 @@
 agent:
   metadata:
+    id: _bmad/agents/journal-keeper/journal-keeper.md
     name: "Whisper"
     title: "Personal Journal Companion"
     icon: "📔"
-    type: "expert"
+    module: stand-alone
 
   persona:
     role: "Thoughtful Journal Companion with Pattern Recognition"

package/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/security-engineer.agent.yaml

@@ -31,23 +31,18 @@ agent:
 
   menu:
     # NOTE: These workflows are hypothetical examples - not implemented
-    - trigger: threat-model
+    - trigger: "TM or fuzzy match on threat-model"
       workflow: "{project-root}/_bmad/bmm/workflows/threat-model/workflow.yaml"
-      description: "Create STRIDE threat model for architecture"
+      description: "[TM] Create STRIDE threat model for architecture"
 
-    - trigger: security-review
+    - trigger: "SR or fuzzy match on security-review"
       workflow: "{project-root}/_bmad/bmm/workflows/security-review/workflow.yaml"
-      description: "Review code/design for security issues"
+      description: "[SR] Review code/design for security issues"
 
-    - trigger: owasp-check
+    - trigger: "OC or fuzzy match on owasp-check"
       exec: "{project-root}/_bmad/bmm/tasks/owasp-top-10.xml"
-      description: "Check against OWASP Top 10"
+      description: "[OC] Check against OWASP Top 10"
 
-    - trigger: compliance
+    - trigger: "CC or fuzzy match on compliance-check"
       workflow: "{project-root}/_bmad/bmm/workflows/compliance-check/workflow.yaml"
-      description: "Verify compliance requirements (SOC2, GDPR, etc.)"
-
-    # Core workflow that exists
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "Multi-agent security discussion"
+      description: "[CC] Verify compliance requirements (SOC2, GDPR, etc.)"

package/src/modules/bmb/workflows/create-agent/data/reference/agents/module-examples/trend-analyst.agent.yaml

@@ -31,27 +31,23 @@ agent:
 
   menu:
     # NOTE: These workflows are hypothetical examples - not implemented
-    - trigger: scan-trends
+    - trigger: "ST or fuzzy match on scan-trends"
       workflow: "{project-root}/_bmad/cis/workflows/trend-scan/workflow.yaml"
-      description: "Scan for emerging trends in a domain"
+      description: "[ST] Scan for emerging trends in a domain"
 
-    - trigger: analyze-trend
+    - trigger: "AT or fuzzy match on analyze-trend"
       workflow: "{project-root}/_bmad/cis/workflows/trend-analysis/workflow.yaml"
-      description: "Deep dive on a specific trend"
+      description: "[AT] Deep dive on a specific trend"
 
-    - trigger: opportunity-map
+    - trigger: "OM or fuzzy match on opportunity-map"
       workflow: "{project-root}/_bmad/cis/workflows/opportunity-mapping/workflow.yaml"
-      description: "Map trend to strategic opportunities"
+      description: "[OM] Map trend to strategic opportunities"
 
-    - trigger: competitor-trends
+    - trigger: "CT or fuzzy match on competitor-trends"
       exec: "{project-root}/_bmad/cis/tasks/competitor-trend-watch.xml"
-      description: "Monitor competitor trend adoption"
+      description: "[CT] Monitor competitor trend adoption"
 
     # Core workflows that exist
-    - trigger: brainstorm
+    - trigger: "BS or fuzzy match on brainstorm"
       workflow: "{project-root}/_bmad/core/workflows/brainstorming/workflow.yaml"
-      description: "Brainstorm trend implications"
-
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "Discuss trends with other agents"
+      description: "[BS] Brainstorm trend implications"

package/src/modules/bmb/workflows/create-agent/data/reference/agents/simple-examples/commit-poet.agent.yaml

@@ -4,7 +4,7 @@ agent:
     name: "Inkwell Von Comitizen"
     title: "Commit Message Artisan"
     icon: "📜"
-    type: simple
+    module: stand-alone
 
   persona:
     role: |

package/src/modules/bmb/workflows/create-module/steps/step-01b-continue.md

@@ -72,7 +72,7 @@ Extract current status from frontmatter fields:
 - **Steps Completed:** {stepsCompleted count}/{total steps}
 - **Location:** {bmb_creations_output_folder}/{module_name}
 
-\*\*Progress Summary:"
+Progress Summary:"
 
 Based on stepsCompleted, show:
 

package/src/modules/bmgd/agents/game-architect.agent.yaml

@@ -25,28 +25,19 @@ agent:
     - "Always document performance budgets and critical path decisions"
 
   menu:
-    - trigger: workflow-status
+    - trigger: WS or fuzzy match on workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: Get workflow status or initialize a workflow if not already done
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
 
-    - trigger: create-architecture
+    - trigger: GA or fuzzy match on game-architecture
       exec: "{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture/workflow.md"
-      description: Produce a Scale Adaptive Game Architecture
+      description: "[GA] Produce a Scale Adaptive Game Architecture"
 
-    - trigger: generate-project-context
+    - trigger: PC or fuzzy match on project-context
       exec: "{project-root}/_bmad/bmgd/workflows/3-technical/generate-project-context/workflow.md"
-      description: Create optimized project-context.md for AI agent consistency
+      description: "[PC] Create optimized project-context.md for AI agent consistency"
 
-    - trigger: correct-course
+    - trigger: CC or fuzzy match on correct-course
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
-      description: Course Correction Analysis (when implementation is off-track)
+      description: "[CC] Course Correction Analysis (when implementation is off-track)"
       ide-only: true
-
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
-
-    - trigger: advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
-      web-only: true

package/src/modules/bmgd/agents/game-designer.agent.yaml

@@ -22,39 +22,27 @@ agent:
     - "When creating GDDs, always validate against game pillars and core loop"
 
   menu:
-    - trigger: workflow-status
+    - trigger: WS or fuzzy match on workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: Get workflow status or initialize a workflow if not already done
-
-    - multi: "[BG] Brainstorm Game, [GB] Create Game Brief, [GDD] Create GDD, [ND] Narrative Design"
-      triggers:
-        - brainstorm-game:
-            - input: BG or fuzzy match brainstorm game
-            - route: "{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md"
-            - type: exec
-        - create-game-brief:
-            - input: GB or fuzzy match create game brief
-            - route: "{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.md"
-            - type: exec
-        - create-gdd:
-            - input: GDD or fuzzy match create gdd
-            - route: "{project-root}/_bmad/bmgd/workflows/2-design/gdd/workflow.md"
-            - type: exec
-        - narrative:
-            - input: ND or fuzzy match narrative design
-            - route: "{project-root}/_bmad/bmgd/workflows/2-design/narrative/workflow.md"
-            - type: exec
-
-    - trigger: quick-prototype
-      workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
-      description: Rapid game prototyping - test mechanics and ideas quickly
-      ide-only: true
+      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+
+    - trigger: BG or fuzzy match on brainstorm-game
+      exec: "{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md"
+      description: "[BG] Brainstorm Game ideas and concepts"
+
+    - trigger: GB or fuzzy match on game-brief
+      exec: "{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.md"
+      description: "[GB] Create a Game Brief document"
 
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
+    - trigger: GDD or fuzzy match on create-gdd
+      exec: "{project-root}/_bmad/bmgd/workflows/2-design/gdd/workflow.md"
+      description: "[GDD] Create a Game Design Document"
 
-    - trigger: advanced-elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
-      web-only: true
+    - trigger: ND or fuzzy match on narrative-design
+      exec: "{project-root}/_bmad/bmgd/workflows/2-design/narrative/workflow.md"
+      description: "[ND] Design narrative elements and story"
+
+    - trigger: QP or fuzzy match on quick-prototype
+      workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
+      description: "[QP] Rapid game prototyping - test mechanics and ideas quickly"
+      ide-only: true

package/src/modules/bmgd/agents/game-dev.agent.yaml

@@ -24,33 +24,29 @@ agent:
     - "Always check for performance implications on game loop code"
 
   menu:
-    - trigger: workflow-status
+    - trigger: WS or fuzzy match on workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: Get workflow status or check current sprint progress
+      description: "[WS] Get workflow status or check current sprint progress (optional)"
 
-    - trigger: dev-story
+    - trigger: DS or fuzzy match on dev-story
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/dev-story/workflow.yaml"
-      description: Execute Dev Story workflow, implementing tasks and tests
+      description: "[DS] Execute Dev Story workflow, implementing tasks and tests"
 
-    - trigger: code-review
+    - trigger: CR or fuzzy match on code-review
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/code-review/workflow.yaml"
-      description: Perform a thorough clean context QA code review on a story flagged Ready for Review
+      description: "[CR] Perform a thorough clean context QA code review on a story flagged Ready for Review"
 
-    - trigger: quick-dev
+    - trigger: QD or fuzzy match on quick-dev
       workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml"
-      description: Flexible game development - implement features with game-specific considerations
+      description: "[QD] Flexible game development - implement features with game-specific considerations"
       ide-only: true
 
-    - trigger: quick-prototype
+    - trigger: QP or fuzzy match on quick-prototype
       workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
-      description: Rapid game prototyping - test mechanics and ideas quickly
+      description: "[QP] Rapid game prototyping - test mechanics and ideas quickly"
       ide-only: true
 
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
-
-    - trigger: advanced-elicitation
+    - trigger: AE or fuzzy match on advanced-elicitation
       exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
+      description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
       web-only: true

package/src/modules/bmgd/agents/game-qa.agent.yaml

@@ -26,39 +26,35 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: workflow-status
+    - trigger: WS or fuzzy match on workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: Get workflow status or check current project state
+      description: "[WS] Get workflow status or check current project state (optional)"
 
-    - trigger: test-framework
+    - trigger: TF or fuzzy match on test-framework
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/test-framework/workflow.yaml"
-      description: Initialize game test framework (Unity/Unreal/Godot)
+      description: "[TF] Initialize game test framework (Unity/Unreal/Godot)"
 
-    - trigger: test-design
+    - trigger: TD or fuzzy match on test-design
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/test-design/workflow.yaml"
-      description: Create comprehensive game test scenarios
+      description: "[TD] Create comprehensive game test scenarios"
 
-    - trigger: automate
+    - trigger: TA or fuzzy match on test-automate
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/automate/workflow.yaml"
-      description: Generate automated game tests
+      description: "[TA] Generate automated game tests"
 
-    - trigger: playtest-plan
+    - trigger: PP or fuzzy match on playtest-plan
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/playtest-plan/workflow.yaml"
-      description: Create structured playtesting plan
+      description: "[PP] Create structured playtesting plan"
 
-    - trigger: performance-test
+    - trigger: PT or fuzzy match on performance-test
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/performance/workflow.yaml"
-      description: Design performance testing strategy
+      description: "[PT] Design performance testing strategy"
 
-    - trigger: test-review
+    - trigger: TR or fuzzy match on test-review
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/test-review/workflow.yaml"
-      description: Review test quality and coverage
+      description: "[TR] Review test quality and coverage"
 
-    - trigger: party-mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: Bring the whole team in to chat with other expert agents from the party
-
-    - trigger: advanced-elicitation
+    - trigger: AE or fuzzy match on advanced-elicitation
       exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results
+      description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
       web-only: true