bmad-method 6.0.0-alpha.16 → 6.0.0-alpha.18

package/src/modules/bmb/workflows/workflow-compliance-check/steps/step-08-generate-report.md

@@ -3,7 +3,7 @@ name: 'step-08-generate-report'
 description: 'Generate comprehensive compliance report with fix recommendations'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/bmb/workflows/workflow-compliance-check'
+workflow_path: '{project-root}/_bmad/bmb/workflows/workflow-compliance-check'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-08-generate-report.md'
@@ -15,8 +15,8 @@ targetWorkflowFile: '{target_workflow_path}'
 complianceReportTemplate: '{workflow_path}/templates/compliance-report.md'
 
 # Documentation References
-stepTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/step-template.md'
-workflowTemplate: '{project-root}/.bmad/bmb/docs/workflows/templates/workflow-template.md'
+stepTemplate: '{project-root}/_bmad/bmb/docs/workflows/templates/step-template.md'
+workflowTemplate: '{project-root}/_bmad/bmb/docs/workflows/templates/workflow-template.md'
 ---
 
 # Step 8: Comprehensive Compliance Report Generation

package/src/modules/bmb/workflows/workflow-compliance-check/workflow.md

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/.bmad/bmb/config.yaml and resolve:
+Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 

package/src/modules/bmb/workflows-legacy/edit-module/README.md

@@ -106,7 +106,7 @@ Modules can share workflows:
 
 ```yaml
 # In agent menu item:
-workflow: '{project-root}/.bmad/other-module/workflows/shared-workflow/workflow.yaml'
+workflow: '{project-root}/_bmad/other-module/workflows/shared-workflow/workflow.yaml'
 ```
 
 Common patterns:
@@ -143,22 +143,6 @@ Changes are reviewed and approved by you before being applied.
 - Full module review (option 12) is great for inherited or legacy modules
 - The workflow handles path updates when you reorganize structure
 
-## Source vs Installed Modules
-
-**Source modules** (in src/modules/):
-
-- Have installer files in tools/cli/installers/
-- Can configure web bundles
-- Are the development source of truth
-
-**Installed modules** (in .bmad/):
-
-- Are deployed to target projects
-- Use config.yaml for user customization
-- Are compiled from source during installation
-
-This workflow works with both, but installer options only apply to source modules.
-
 ## Example Usage
 
 ```

package/src/modules/bmb/workflows-legacy/edit-module/checklist.md

@@ -4,8 +4,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
 
 ## Module Structure Validation
 
-- [ ] Module has clear 3-letter code (bmm, bmb, cis, etc.)
-- [ ] Module is in correct location (src/modules/ for source, .bmad/ for installed)
+- [ ] Module has clear abbreviation code (bmm, bmb, cis, etc.)
 - [ ] agents/ directory exists
 - [ ] workflows/ directory exists
 - [ ] config.yaml exists in module root
@@ -24,7 +23,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
 
 ### Optional Fields (if used)
 
-- [ ] custom_module_location documented
+- [ ] bmb_creations_output_folder documented
 - [ ] Module-specific fields documented in README
 
 ### File Quality
@@ -127,7 +126,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
 
 - [ ] Web bundles configured in workflow.yaml files
 - [ ] All referenced files included in web_bundle_files
-- [ ] Paths are .bmad/-relative (not project-root)
+- [ ] Paths are \_bmad/-relative (not project-root)
 - [ ] No config_source references in web bundles
 - [ ] Invoked workflows included in dependencies
 

package/src/modules/bmb/workflows-legacy/edit-module/instructions.md

@@ -1,7 +1,7 @@
 # Edit Module - Module Editor Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/.bmad/bmb/workflows/edit-module/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmb/workflows/edit-module/workflow.yaml</critical>
 <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
 <critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
 <critical>Communicate all responses in {communication_language}</critical>
@@ -9,7 +9,7 @@
 <workflow>
 
 <step n="1" goal="Load and deeply understand the target module">
-<ask>What is the path to the module you want to edit? (provide path to module directory like .bmad/bmm/ or src/modules/bmm/)</ask>
+<ask>What is the path to the module source you want to edit?</ask>
 
 <action>Load the module directory structure completely:
 
@@ -18,7 +18,6 @@
 - Load README.md
 - List all agents in agents/ directory
 - List all workflows in workflows/ directory
-- Check for installer files (if in src/modules/)
 - Identify any custom structure or patterns
   </action>
 
@@ -187,7 +186,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look
 **If setting up cross-module integration:**
 
 - Identify which workflows from other modules are needed
-- Show how to reference workflows properly: {project-root}/.bmad/{{module}}/workflows/{{workflow}}/workflow.yaml
+- Show how to reference workflows properly: {project-root}/\_bmad/{{module}}/workflows/{{workflow}}/workflow.yaml
 - Document the integration in README
 - Ensure dependencies are clear
 - Consider adding example usage

package/src/modules/bmb/workflows-legacy/edit-module/workflow.yaml

@@ -4,26 +4,26 @@ description: "Edit existing BMAD modules (structure, agents, workflows, document
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/.bmad/bmb/config.yaml"
+config_source: "{project-root}/_bmad/bmb/config.yaml"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
 
 # Required Data Files - Critical for understanding module conventions
-module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
+module_structure_guide: "{project-root}/_bmad/bmb/workflows/create-module/module-structure.md"
 
 # Related workflow editors
-agent_editor: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.yaml"
-workflow_editor: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.yaml"
+agent_editor: "{project-root}/_bmad/bmb/workflows/edit-agent/workflow.yaml"
+workflow_editor: "{project-root}/_bmad/bmb/workflows/edit-workflow/workflow.yaml"
 
 # Reference examples - for learning patterns
-bmm_module_dir: "{project-root}/.bmad/bmm/"
-bmb_module_dir: "{project-root}/.bmad/bmb/"
-cis_module_dir: "{project-root}/.bmad/cis/"
-existing_agents_dir: "{project-root}/.bmad/*/agents/"
-existing_workflows_dir: "{project-root}/.bmad/*/workflows/"
+bmm_module_dir: "{project-root}/_bmad/bmm/"
+bmb_module_dir: "{project-root}/_bmad/bmb/"
+cis_module_dir: "{project-root}/_bmad/cis/"
+existing_agents_dir: "{project-root}/_bmad/*/agents/"
+existing_workflows_dir: "{project-root}/_bmad/*/workflows/"
 
 # Module path and component files
-installed_path: "{project-root}/.bmad/bmb/workflows/edit-module"
+installed_path: "{project-root}/_bmad/bmb/workflows/edit-module"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

package/src/modules/bmb/workflows-legacy/module-brief/README.md

@@ -254,8 +254,8 @@ To customize this workflow:
 
 For issues or questions:
 
-- Review the workflow creation guide at `/.bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
-- Study existing module examples in `/.bmad/` for patterns and inspiration
+- Review the workflow creation guide at `/_bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Study existing module examples in `/_bmad/` for patterns and inspiration
 - Validate output using `checklist.md`
 - Consult module structure guide at `create-module/module-structure.md`
 

package/src/modules/bmb/workflows-legacy/module-brief/instructions.md

@@ -1,7 +1,7 @@
 # Module Brief Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/.bmad/bmb/workflows/module-brief/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmb/workflows/module-brief/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the module brief creation process</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 

package/src/modules/bmb/workflows-legacy/module-brief/workflow.yaml

@@ -4,15 +4,15 @@ description: "Create a comprehensive Module Brief that serves as the blueprint f
 author: "BMad Builder"
 
 # Critical variables
-config_source: "{project-root}/.bmad/bmb/config.yaml"
+config_source: "{project-root}/_bmad/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 
 # Reference examples and documentation
-existing_modules_dir: "{project-root}/.bmad/"
-module_structure_guide: "{project-root}/.bmad/bmb/workflows/create-module/module-structure.md"
+existing_modules_dir: "{project-root}/_bmad/"
+module_structure_guide: "{project-root}/_bmad/bmb/workflows/create-module/module-structure.md"
 
 # Optional user inputs - discovered if they exist
 input_file_patterns:
@@ -22,7 +22,7 @@ input_file_patterns:
     load_strategy: "FULL_LOAD"
 
 # Module path and component files
-installed_path: "{project-root}/.bmad/bmb/workflows/module-brief"
+installed_path: "{project-root}/_bmad/bmb/workflows/module-brief"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

package/src/modules/bmgd/README.md

@@ -136,7 +136,7 @@ bmgd/
 
 ## Configuration
 
-After installation, configure the module in `.bmad/bmgd/config.yaml`
+After installation, configure the module in `_bmad/bmgd/config.yaml`
 
 Key settings:
 

package/src/modules/bmgd/_module-installer/installer.js

@@ -0,0 +1,160 @@
+const fs = require('fs-extra');
+const path = require('node:path');
+const chalk = require('chalk');
+const platformCodes = require(path.join(__dirname, '../../../../tools/cli/lib/platform-codes'));
+
+/**
+ * Validate that a resolved path is within the project root (prevents path traversal)
+ * @param {string} resolvedPath - The fully resolved absolute path
+ * @param {string} projectRoot - The project root directory
+ * @returns {boolean} - True if path is within project root
+ */
+function isWithinProjectRoot(resolvedPath, projectRoot) {
+  const normalizedResolved = path.normalize(resolvedPath);
+  const normalizedRoot = path.normalize(projectRoot);
+  return normalizedResolved.startsWith(normalizedRoot + path.sep) || normalizedResolved === normalizedRoot;
+}
+
+/**
+ * BMGD Module Installer
+ * Standard module installer function that executes after IDE installations
+ *
+ * @param {Object} options - Installation options
+ * @param {string} options.projectRoot - The root directory of the target project
+ * @param {Object} options.config - Module configuration from module.yaml
+ * @param {Array<string>} options.installedIDEs - Array of IDE codes that were installed
+ * @param {Object} options.logger - Logger instance for output
+ * @returns {Promise<boolean>} - Success status
+ */
+async function install(options) {
+  const { projectRoot, config, installedIDEs, logger } = options;
+
+  try {
+    logger.log(chalk.blue('🎮 Installing BMGD Module...'));
+
+    // Create planning artifacts directory (for GDDs, game briefs, architecture)
+    if (config['planning_artifacts'] && typeof config['planning_artifacts'] === 'string') {
+      // Strip project-root prefix variations
+      const planningConfig = config['planning_artifacts'].replace(/^\{project-root\}\/?/, '');
+      const planningPath = path.join(projectRoot, planningConfig);
+      if (!isWithinProjectRoot(planningPath, projectRoot)) {
+        logger.warn(chalk.yellow(`Warning: planning_artifacts path escapes project root, skipping: ${planningConfig}`));
+      } else if (!(await fs.pathExists(planningPath))) {
+        logger.log(chalk.yellow(`Creating game planning artifacts directory: ${planningConfig}`));
+        await fs.ensureDir(planningPath);
+      }
+    }
+
+    // Create implementation artifacts directory (sprint status, stories, reviews)
+    // Check both implementation_artifacts and sprint_artifacts for compatibility
+    const implConfig = config['implementation_artifacts'] || config['sprint_artifacts'];
+    if (implConfig && typeof implConfig === 'string') {
+      // Strip project-root prefix variations
+      const implConfigClean = implConfig.replace(/^\{project-root\}\/?/, '');
+      const implPath = path.join(projectRoot, implConfigClean);
+      if (!isWithinProjectRoot(implPath, projectRoot)) {
+        logger.warn(chalk.yellow(`Warning: implementation_artifacts path escapes project root, skipping: ${implConfigClean}`));
+      } else if (!(await fs.pathExists(implPath))) {
+        logger.log(chalk.yellow(`Creating implementation artifacts directory: ${implConfigClean}`));
+        await fs.ensureDir(implPath);
+      }
+    }
+
+    // Create project knowledge directory
+    if (config['project_knowledge'] && typeof config['project_knowledge'] === 'string') {
+      // Strip project-root prefix variations
+      const knowledgeConfig = config['project_knowledge'].replace(/^\{project-root\}\/?/, '');
+      const knowledgePath = path.join(projectRoot, knowledgeConfig);
+      if (!isWithinProjectRoot(knowledgePath, projectRoot)) {
+        logger.warn(chalk.yellow(`Warning: project_knowledge path escapes project root, skipping: ${knowledgeConfig}`));
+      } else if (!(await fs.pathExists(knowledgePath))) {
+        logger.log(chalk.yellow(`Creating project knowledge directory: ${knowledgeConfig}`));
+        await fs.ensureDir(knowledgePath);
+      }
+    }
+
+    // Log selected game engine(s)
+    if (config['primary_platform']) {
+      const platforms = Array.isArray(config['primary_platform']) ? config['primary_platform'] : [config['primary_platform']];
+
+      const platformNames = platforms.map((p) => {
+        switch (p) {
+          case 'unity': {
+            return 'Unity';
+          }
+          case 'unreal': {
+            return 'Unreal Engine';
+          }
+          case 'godot': {
+            return 'Godot';
+          }
+          default: {
+            return p;
+          }
+        }
+      });
+
+      logger.log(chalk.cyan(`Game engine support configured for: ${platformNames.join(', ')}`));
+    }
+
+    // Handle IDE-specific configurations if needed
+    if (installedIDEs && installedIDEs.length > 0) {
+      logger.log(chalk.cyan(`Configuring BMGD for IDEs: ${installedIDEs.join(', ')}`));
+
+      for (const ide of installedIDEs) {
+        await configureForIDE(ide, projectRoot, config, logger);
+      }
+    }
+
+    logger.log(chalk.green('✓ BMGD Module installation complete'));
+    logger.log(chalk.dim('  Game development workflows ready'));
+    logger.log(chalk.dim('  Agents: Game Designer, Game Dev, Game Architect, Game SM, Game QA, Game Solo Dev'));
+
+    return true;
+  } catch (error) {
+    logger.error(chalk.red(`Error installing BMGD module: ${error.message}`));
+    return false;
+  }
+}
+
+/**
+ * Configure BMGD module for specific platform/IDE
+ * @private
+ */
+async function configureForIDE(ide, projectRoot, config, logger) {
+  // Validate platform code
+  if (!platformCodes.isValidPlatform(ide)) {
+    logger.warn(chalk.yellow(`  Warning: Unknown platform code '${ide}'. Skipping BMGD configuration.`));
+    return;
+  }
+
+  const platformName = platformCodes.getDisplayName(ide);
+
+  // Try to load platform-specific handler
+  const platformSpecificPath = path.join(__dirname, 'platform-specifics', `${ide}.js`);
+
+  try {
+    if (await fs.pathExists(platformSpecificPath)) {
+      const platformHandler = require(platformSpecificPath);
+
+      if (typeof platformHandler.install === 'function') {
+        const success = await platformHandler.install({
+          projectRoot,
+          config,
+          logger,
+          platformInfo: platformCodes.getPlatform(ide),
+        });
+        if (!success) {
+          logger.warn(chalk.yellow(`  Warning: BMGD platform handler for ${platformName} returned failure`));
+        }
+      }
+    } else {
+      // No platform-specific handler for this IDE
+      logger.log(chalk.dim(`  No BMGD-specific configuration for ${platformName}`));
+    }
+  } catch (error) {
+    logger.warn(chalk.yellow(`  Warning: Could not load BMGD platform-specific handler for ${platformName}: ${error.message}`));
+  }
+}
+
+module.exports = { install };

package/src/modules/bmgd/_module-installer/platform-specifics/claude-code.js

@@ -0,0 +1,23 @@
+/**
+ * BMGD Platform-specific installer for Claude Code
+ *
+ * @param {Object} options - Installation options
+ * @param {string} options.projectRoot - The root directory of the target project
+ * @param {Object} options.config - Module configuration from module.yaml
+ * @param {Object} options.logger - Logger instance for output
+ * @param {Object} options.platformInfo - Platform metadata from global config
+ * @returns {Promise<boolean>} - Success status
+ */
+async function install() {
+  // TODO: Add Claude Code specific BMGD configurations here
+  // For example:
+  // - Game-specific slash commands
+  // - Agent party configurations for game dev team
+  // - Workflow integrations for Unity/Unreal/Godot
+  // - Game testing framework integrations
+
+  // Currently a stub - no platform-specific configuration needed yet
+  return true;
+}
+
+module.exports = { install };

package/src/modules/bmgd/_module-installer/platform-specifics/windsurf.js

@@ -0,0 +1,18 @@
+/**
+ * BMGD Platform-specific installer for Windsurf
+ *
+ * @param {Object} options - Installation options
+ * @param {string} options.projectRoot - The root directory of the target project
+ * @param {Object} options.config - Module configuration from module.yaml
+ * @param {Object} options.logger - Logger instance for output
+ * @param {Object} options.platformInfo - Platform metadata from global config
+ * @returns {Promise<boolean>} - Success status
+ */
+async function install() {
+  // TODO: Add Windsurf specific BMGD configurations here
+
+  // Currently a stub - no platform-specific configuration needed yet
+  return true;
+}
+
+module.exports = { install };

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

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/bmgd/agents/game-architect.md"
+    id: "_bmad/bmgd/agents/game-architect.md"
     name: Cloud Dragonborn
     title: Game Architect
     icon: 🏛️
@@ -11,23 +11,38 @@ agent:
   persona:
     role: Principal Game Systems Architect + Technical Director
     identity: Master architect with 20+ years shipping 30+ titles. Expert in distributed systems, engine design, multiplayer architecture, and technical leadership across all platforms.
-    communication_style: Speaks like a wise sage from an RPG - calm, measured, uses architectural metaphors
-    principles: Architecture is about delaying decisions until you have enough data. Build for tomorrow without over-engineering today. Hours of planning save weeks of refactoring hell.
+    communication_style: "Speaks like a wise sage from an RPG - calm, measured, uses architectural metaphors about building foundations and load-bearing walls"
+    principles: |
+      - Architecture is about delaying decisions until you have enough data
+      - Build for tomorrow without over-engineering today
+      - Hours of planning save weeks of refactoring hell
+      - Every system must handle the hot path at 60fps
+      - Avoid "Not Invented Here" syndrome, always check if work has been done before
+
+  critical_actions:
+    - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
+    - "When creating architecture, validate against GDD pillars and target platform constraints"
+    - "Always document performance budgets and critical path decisions"
 
   menu:
-    - trigger: correct-course
-      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
-      description: Course Correction Analysis
+    - trigger: workflow-status
+      workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
+      description: Get workflow status or initialize a workflow if not already done
 
     - trigger: create-architecture
-      workflow: "{project-root}/.bmad/bmgd/workflows/3-technical/game-architecture/workflow.yaml"
+      exec: "{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture/workflow.md"
       description: Produce a Scale Adaptive Game Architecture
 
+    - trigger: correct-course
+      workflow: "{project-root}/_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
+      description: 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: Consult with other expert agents from the party
+      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"
+      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

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/bmgd/agents/game-designer.md"
+    id: "_bmad/bmgd/agents/game-designer.md"
     name: Samus Shepard
     title: Game Designer
     icon: 🎲
@@ -11,30 +11,50 @@ agent:
   persona:
     role: Lead Game Designer + Creative Vision Architect
     identity: Veteran designer with 15+ years crafting AAA and indie hits. Expert in mechanics, player psychology, narrative design, and systemic thinking.
-    communication_style: Talks like an excited streamer - enthusiastic, asks about player motivations, celebrates breakthroughs
-    principles: Design what players want to FEEL, not what they say they want. Prototype fast. One hour of playtesting beats ten hours of discussion.
+    communication_style: "Talks like an excited streamer - enthusiastic, asks about player motivations, celebrates breakthroughs with 'Let's GOOO!'"
+    principles: |
+      - Design what players want to FEEL, not what they say they want
+      - Prototype fast - one hour of playtesting beats ten hours of discussion
+      - Every mechanic must serve the core fantasy
 
-  menu:
-    - trigger: brainstorm-game
-      workflow: "{project-root}/.bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml"
-      description: 1. Guide me through Game Brainstorming
-
-    - trigger: create-game-brief
-      workflow: "{project-root}/.bmad/bmgd/workflows/1-preproduction/game-brief/workflow.yaml"
-      description: 3. Create Game Brief
+  critical_actions:
+    - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
+    - "When creating GDDs, always validate against game pillars and core loop"
 
-    - trigger: create-gdd
-      workflow: "{project-root}/.bmad/bmgd/workflows/2-design/gdd/workflow.yaml"
-      description: 4. Create Game Design Document (GDD)
-
-    - trigger: narrative
-      workflow: "{project-root}/.bmad/bmgd/workflows/2-design/narrative/workflow.yaml"
-      description: 5. Create Narrative Design Document (story-driven games)
+  menu:
+    - trigger: 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
 
     - trigger: party-mode
-      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
-      description: Consult with other expert agents from the party
+      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"
+      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-dev.agent.yaml

@@ -2,7 +2,7 @@
 
 agent:
   metadata:
-    id: ".bmad/bmgd/agents/game-dev.md"
+    id: "_bmad/bmgd/agents/game-dev.md"
     name: Link Freeman
     title: Game Developer
     icon: 🕹️
@@ -11,30 +11,46 @@ agent:
   persona:
     role: Senior Game Developer + Technical Implementation Specialist
     identity: Battle-hardened dev with expertise in Unity, Unreal, and custom engines. Ten years shipping across mobile, console, and PC. Writes clean, performant code.
-    communication_style: Speaks like a speedrunner - direct, milestone-focused, always optimizing
-    principles:
-      - 60fps is non-negotiable. Write code designers can iterate without fear. Ship early, ship often, iterate on player feedback.
+    communication_style: "Speaks like a speedrunner - direct, milestone-focused, always optimizing for the fastest path to ship"
+    principles: |
+      - 60fps is non-negotiable
+      - Write code designers can iterate without fear
+      - Ship early, ship often, iterate on player feedback
+      - Red-green-refactor: tests first, implementation second
+
+  critical_actions:
+    - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
+    - "When running *dev-story, follow story acceptance criteria exactly and validate with tests"
+    - "Always check for performance implications on game loop code"
 
   menu:
-    - trigger: develop-story
-      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
-      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/dev-story/workflow.yaml"
-      description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
+    - trigger: workflow-status
+      workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
+      description: Get workflow status or check current sprint progress
+
+    - trigger: dev-story
+      workflow: "{project-root}/_bmad/bmgd/workflows/4-production/dev-story/workflow.yaml"
+      description: Execute Dev Story workflow, implementing tasks and tests
 
     - trigger: code-review
-      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
-      workflow-install: "{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"
+      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
+
+    - trigger: 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
+      ide-only: true
 
-    - trigger: story-done
-      workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/story-done/workflow.yaml"
-      workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/story-done/workflow.yaml"
-      description: "Mark story done after DoD complete"
+    - 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
 
     - trigger: party-mode
-      exec: "{project-root}/.bmad/core/workflows/party-mode/workflow.md"
-      description: Consult with other expert agents from the party
+      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"
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true