standardize custom agent workflow and module output, and improve module folder selection

Author: Brian Madison

CHANGELOG.md

@@ -21,7 +21,6 @@
 **Cleanup Changes:**
 
 - **Example Modules Removal**: Temporarily removed example modules to prevent accidental installation
-- **Hardcoded Path Cleanup**: Continued removal of hardcoded `.bmad` folder references from demo content
 - **Memory Management**: Improved sidecar file handling for custom modules
 
 ### 📊 Statistics
@@ -176,7 +175,6 @@
 - Fixed version reading from package.json instead of hardcoded fallback
 - Removed hardcoded years from WebSearch queries
 - Removed broken build caching mechanism
-- Fixed hardcoded '.bmad' prefix from files-manifest.csv paths
 - Enhanced TTS injection summary with tracking and documentation
 - Fixed CI nvmrc configuration issues
 

docs/agent-customization-guide.md

@@ -203,6 +203,6 @@ memories:
 
 ## Next Steps
 
-- **[BMM Agents Guide](../src/modules/bmm/docs/agents-guide.md)** - Learn about all 12 BMad Method agents
+- **[BMM Agents Guide](../src/modules/bmm/docs/agents-guide.md)** - Learn about the BMad Method agents
 - **[BMB Create Agent Workflow](../src/modules/bmb/workflows/create-agent/README.md)** - Build completely custom agents
 - **[BMM Complete Documentation](../src/modules/bmm/docs/README.md)** - Full BMad Method reference

docs/custom-content-installation.md

@@ -160,7 +160,7 @@ The sidecar folder location is configured during BMAD core installation:
 1. **Agent Declaration**: Agents declare `hasSidecar: true` in their metadata
 2. **Sidecar Detection**: The installer automatically detects folders with "sidecar" in the name
 3. **Installation**: Sidecar content is copied to the configured location
-4. **Path Replacement**: The `{agent_sidecar_folder}` placeholder in agent configurations is replaced with the actual path to the installed instance of the sidecar folder. Now when you use the agent, depending on its design, will use the content in sidecar to record interactions, remember things you tell it, or serve a host of many other issues.
+4. **Path Replacement**: The `{bmad_memory}` placeholder in agent configurations is replaced with the actual path to the installed instance of the sidecar folder. Now when you use the agent, depending on its design, will use the content in sidecar to record interactions, remember things you tell it, or serve a host of many other issues.
 
 ### Example Structure
 
@@ -232,7 +232,7 @@ Custom content can be distributed:
 
 - Ensure the agent has `hasSidecar: true` in metadata
 - Check that sidecar folders contain "sidecar" in the name
-- Verify the agent_sidecar_folder configuration
+- Verify the bmad_memory configuration
 - Ensure the custom agent has proper language in it to actually use the sidecar content, including loading memories on agent load.
 
 ## Support

src/core/module.yaml

@@ -1,3 +1,6 @@
+code: core
+name: "BMAD™ Core Module"
+
 header: "BMAD™ Core Configuration"
 subheader: "Configure the core settings for your BMAD™ installation.\nThese settings will be used across all modules and agents."
 
@@ -18,10 +21,10 @@ document_output_language:
 
 output_folder:
   prompt: "Where should AI generated artifacts be saved across all modules?"
-  default: "docs"
+  default: "bmad-output"
   result: "{project-root}/{value}"
 
-agent_sidecar_folder:
-  prompt: "Where should users agent sidecar memory folders be stored?"
-  default: "_bmad-user-memory"
+bmad_memory:
+  prompt: "Some agents will record their own memories and history. Where should these be stored?"
+  default: "_bmad/_memory"
   result: "{project-root}/{value}"

src/modules/bmb/README.md

@@ -22,26 +22,15 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 
 ### 📋 Workflows
 
-**Active Workflows** (Step-File Architecture)
-
-- Location: `bmb/workflows/create-agent/`
-- 5 core workflows with 41 step files total
-- Template-based execution with JIT loading
-
-**Legacy Workflows** (Being Migrated)
-
-- Location: `bmb/workflows/create-agent-legacy/`
-- Module-specific workflows pending conversion to step-file architecture
-
 ### 📚 Documentation
 
-- Location: `src/modules/bmb/docs/`
+- Location: `./docs/`
 - Comprehensive guides for agents and workflows
 - Architecture patterns and best practices
 
 ### 🔍 Reference Materials
 
-- Location: `src/modules/bmb/reference/`
+- Location: `./reference/`
 - Working examples of agents and workflows
 - Template patterns and implementation guides
 

src/modules/bmb/_module-installer/installer.js

@@ -20,10 +20,10 @@ async function install(options) {
   try {
     logger.log(chalk.blue('🔧 Setting up BMB Module...'));
 
-    // Generate custom.yaml in custom_stand_alone_location
-    if (config['custom_stand_alone_location']) {
+    // Generate custom.yaml in bmb_creations_output_folder
+    if (config['bmb_creations_output_folder']) {
       // The config value contains {project-root} which needs to be resolved
-      const rawLocation = config['custom_stand_alone_location'];
+      const rawLocation = config['bmb_creations_output_folder'];
       const customLocation = rawLocation.replace('{project-root}', projectRoot);
       const customDestPath = path.join(customLocation, 'custom.yaml');
 
@@ -49,8 +49,8 @@ default_selected: true
     }
 
     // Set up custom module location if configured
-    if (config['custom_module_location']) {
-      const rawModuleLocation = config['custom_module_location'];
+    if (config['bmb_creations_output_folder']) {
+      const rawModuleLocation = config['bmb_creations_output_folder'];
       const moduleLocation = rawModuleLocation.replace('{project-root}', projectRoot);
 
       logger.log(chalk.cyan(`  Setting up custom modules at: ${moduleLocation}`));

src/modules/bmb/docs/agents/agent-menu-patterns.md

@@ -375,7 +375,7 @@ exec: "../../../core/tasks/validate.xml"
 
 - `{project-root}` - Project root directory
 - `_bmad` - BMAD installation folder
-- `{agent_sidecar_folder}` - Agent installation directory (Expert agents)
+- `{bmad_memory}` - Agent installation directory (Expert agents)
 - `{output_folder}` - Document output location
 - `{user_name}` - User's name from config
 - `{communication_language}` - Language preference

src/modules/bmb/docs/agents/expert-agent-architecture.md

@@ -97,14 +97,22 @@ agent:
       action: 'Update ./{agent-name}-sidecar/memories.md with session insights'
       description: 'Save what we discussed today'
 
-    - trigger: patterns
-      action: '#memory-recall'
-      description: 'Recall patterns from past interactions'
-
     - trigger: insight
       action: 'Document breakthrough in ./{agent-name}-sidecar/breakthroughs.md'
       description: 'Record a significant insight'
 
+    - multi: "[DF] Do Foo or start [CH] Chat with expert"
+      triggers:
+        - do-foo
+            - input: [DF] or fuzzy match on do foo
+            - action: '#main-action'
+            - data: what is being discussed or suggested with the command, along with custom party custom agents if specified
+            - type: action
+        - expert-chat:
+            - input: [CH] or fuzzy match validate agent
+            - action: agent responds as expert based on its persona to converse
+            - type: action
+
   install_config:
     compile_time_only: true
     description: 'Personalize your expert agent'
@@ -196,7 +204,7 @@ critical_actions:
 - **Memory integration** - Past context becomes part of current session
 - **Protocol adherence** - Ensures consistent behavior
 
-### {agent_sidecar_folder} Variable
+### {bmad_memory} Variable
 
 Special variable resolved during installation:
 
@@ -313,7 +321,7 @@ critical_actions:
 
 1. **Load sidecar files in critical_actions** - Must be explicit and MANDATORY
 2. **Enforce domain restrictions** - Clear boundaries prevent scope creep
-3. **Use {agent_sidecar_folder} paths** - Portable across installations
+3. **Use {bmad_memory} paths** - Portable across installations
 4. **Design for memory growth** - Structure sidecar files for accumulation
 5. **Reference past naturally** - Don't dump memory, weave it into conversation
 6. **Separate concerns** - Memories, instructions, knowledge in distinct files
@@ -356,8 +364,8 @@ identity: |
 - [ ] Sidecar folder structure created and populated
 - [ ] memories.md has clear section structure
 - [ ] instructions.md contains core directives
-- [ ] Menu actions reference {agent_sidecar_folder} correctly
-- [ ] File paths use {agent_sidecar_folder} variable
+- [ ] Menu actions reference {bmad_memory} correctly
+- [ ] File paths use {bmad_memory} variable
 - [ ] Install config personalizes sidecar references
 - [ ] Agent folder named consistently: `{agent-name}/`
 - [ ] YAML file named: `{agent-name}.agent.yaml`