bmad-method 6.0.0-alpha.14 → 6.0.0-alpha.15

package/docs/custom-content-installation.md

@@ -0,0 +1,245 @@
+# Custom Content Installation
+
+This guide explains how to create and install custom BMAD content including agents, workflows, and modules. Custom content allows you to extend BMAD's functionality with your own specialized tools and workflows that can be shared across projects or teams.
+
+## Types of Custom Content
+
+### 1. Custom Agents and Workflows (Standalone)
+
+Custom agents and workflows are standalone content packages that can be installed without being part of a full module. These are perfect for:
+
+- Sharing specialized agents across projects
+- Building a personal Agent powered Notebook vault
+- Distributing workflow templates
+- Creating agent libraries for specific domains
+
+#### Structure
+
+A custom agents and workflows package follows this structure:
+
+```
+my-custom-agents/
+├── module.yaml          # Package configuration
+├── agents/              # Agent definitions
+│   └── my-agent/
+│       └── agent.md
+└── workflows/           # Workflow definitions
+    └── my-workflow/
+        └── workflow.md
+```
+
+#### Configuration
+
+Create a `module.yaml` file in your package root:
+
+```yaml
+code: my-custom-agents
+name: 'My Custom Agents and Workflows'
+default_selected: true
+```
+
+#### Example
+
+See `/example-custom-content` for a working example of a folder with multiple random custom agents and workflows. Technically its also just a module, but you will be able to further pick and choose from this folders contents of what you do and do not want to include in a destination folder. This way, you can store all custom content source in one location and easily install it to different locations.
+
+### 2. Custom Modules
+
+Custom modules are complete BMAD modules that can include their own configuration, documentation, along with agents and workflows that all compliment each other. Additionally they will have their own installation scripts, data, and potentially other tools. Modules can be used for:
+
+- Domain-specific functionality (e.g., industry-specific workflows, entertainment, education and training, medical, etc...)
+- Integration with external systems
+- Specialized agent collections
+- Custom tooling and utilities
+
+#### Structure
+
+A custom module follows this structure:
+
+```
+my-module/
+├── _module-installer/
+│   ├── installer.js           # optional, when it exists it will run with module installation
+├── module.yaml                # Module installation configuration with custom question and answer capture
+├── docs/                      # Module documentation
+├── agents/                    # Module-specific agents
+├── workflows/                 # Module-specific workflows
+├── data/                      # csv or other content to power agent intelligence or workflows
+├── tools/                     # Custom tools, hooks, mcp
+└── sub-modules/               # IDE-specific customizations
+    ├── vscode/
+    └── cursor/
+```
+
+#### Module Configuration
+
+The `module.yaml` file defines how your module is installed:
+
+```yaml
+# Module metadata
+code: my-module
+name: 'My Custom Module'
+default_selected: false
+
+header: 'My Custom Module'
+subheader: 'Description of what this module does'
+
+# Configuration prompts
+my_setting:
+  prompt: 'Configure your module setting'
+  default: 'default-value'
+  result: '{value}'
+```
+
+#### Example
+
+See `/example-custom-module` for a complete example:
+
+## Installation Process
+
+### Step 1: Running the Installer
+
+When you run the existing normal BMAD installer - either from the cloned repo, OR via NPX, it will ask about custom content:
+
+```
+? Do you have custom content to install?
+❯ No (skip custom content)
+  Enter a directory path
+  Enter a URL [Coming soon]
+```
+
+### Step 2: Providing Custom Content Path
+
+If you select "Enter a directory path", the installer will prompt for the location:
+
+```
+? Enter the path to your custom content directory: /path/to/folder/containing/content/folder
+```
+
+The installer will:
+
+- Scan for `module.yaml` files (modules)
+- Display an indication of how many installable folders it has found. Note that a project with stand along agents and workflows all under a single folder like the example will just list the count as 1 for that directory.
+
+### Step 3: Selecting Content
+
+The installer presents a unified selection interface:
+
+```
+? Select modules and custom content to install:
+[── Custom Content ──]
+ ◉ My Custom Agents and Workflows (/path/to/custom)
+[── Official Content ──]
+ ◯ BMM: Business Method & Management
+ ◯ CIS: Creativity & Innovation Suite
+```
+
+## Agent Sidecar Support
+
+Agents with sidecar content can store personal data, memories, and working files outside of the `.bmad` directory. This separation keeps personal content separate from BMAD's core files.
+
+### What is Sidecar Content?
+
+Sidecar content includes:
+
+- Agent memories and learning data
+- Personal working files
+- Temporary data
+- User-specific configurations
+
+### Sidecar Configuration
+
+The sidecar folder location is configured during BMAD core installation:
+
+```
+? Where should users' agent sidecar memory folders be stored?
+❯ .bmad-user-memory
+```
+
+### How It Works
+
+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.
+
+### Example Structure
+
+```
+my-agent/
+├── agent.md              # Agent definition
+└── my-agent-sidecar/     # Sidecar content folder
+    ├── memories/
+    ├── working/
+    └── config/
+```
+
+### Git Integration
+
+Since sidecar content is stored outside the `.bmad` directory (and typically outside version control), users can:
+
+- Add the sidecar folder to `.gitignore` to exclude personal data
+- Share agent definitions without exposing personal content
+- Maintain separate configurations for different projects
+
+Example `.gitignore` entry:
+
+```
+# Exclude agent personal data
+.bmad-user-memory/
+```
+
+## Creating Custom Content with BMAD Builder
+
+The BMAD Builder provides workflows that will guide you to produce your own custom content:
+
+1. **Agent Templates**: Use standardized agent templates with proper structure
+2. **Workflow Templates**: Create workflows using proven patterns
+3. **Validation Tools**: Validate your content before distribution
+4. **Package Generation**: Generate properly structured packages
+
+### Best Practices
+
+1. **Use Clear Naming**: Make your content codes and names descriptive
+2. **Provide Documentation**: Include clear setup and usage instructions
+3. **Test Installation**: Test your content in a clean environment
+4. **Version Management**: Use semantic versioning for updates
+5. **Respect User Privacy**: Keep personal data in sidecar folders
+
+## Distribution
+
+Custom content can be distributed:
+
+1. **File System**: Copy folders directly to users
+2. **Git Repositories**: Clone or download from version control
+3. **Package Managers**: [Coming soon] npm package support
+4. **URL Installation**: [Coming soon] Direct URL installation, including an official community vetted module forge
+
+## Troubleshooting
+
+### No Custom Content Found
+
+- Ensure your `module.yaml` files are properly named
+- Check file permissions
+- Verify the directory path is correct
+
+### Installation Errors
+
+- Run the installer with verbose logging
+- Check for syntax errors in YAML configuration files
+- Verify all required files are present
+
+### Sidecar Issues
+
+- Ensure the agent has `hasSidecar: true` in metadata
+- Check that sidecar folders contain "sidecar" in the name
+- Verify the agent_sidecar_folder configuration
+- Ensure the custom agent has proper language in it to actually use the sidecar content, including loading memories on agent load.
+
+## Support
+
+For help with custom content creation or installation:
+
+1. Check the examples in `/example-custom-content` and `/example-custom-module`
+2. Review the BMAD documentation
+3. Create an issue in the BMAD repository
+4. Join the BMAD community discussions on discord

package/docs/index.md

@@ -96,9 +96,9 @@ Instructions for loading agents and running workflows in your development enviro
 
 ## 🔧 Advanced Topics
 
-### Custom Agents
+### Custom Agents, Workflow and Modules
 
-- **[Custom Agent Installation](./custom-agent-installation.md)** - Install and personalize agents with `bmad agent-install`
+- **[Custom Content Installation](./custom-content-installation.md)** - Install and personalize agents, workflows and modules with the default bmad-method installer!
 - [Agent Customization Guide](./agent-customization-guide.md) - Customize agent behavior and responses
 
 ### Installation & Bundling

package/docs/installers-bundlers/installers-modules-platforms-reference.md

@@ -59,6 +59,7 @@ project-root/
 ### Key Exclusions
 
 - `_module-installer/` directories are never copied to destination
+- module.yaml
 - `localskip="true"` agents are filtered out
 - Source `config.yaml` templates are replaced with generated configs
 
@@ -92,8 +93,8 @@ Creative Innovation Studio for design workflows
 ```
 src/modules/{module}/
 ├── _module-installer/       # Not copied to destination
-│   ├── installer.js        # Post-install logic
-│   └── install-config.yaml
+│   ├── installer.js         # Post-install logic
+├── module.yaml
 ├── agents/
 ├── tasks/
 ├── templates/
@@ -107,7 +108,7 @@ src/modules/{module}/
 
 ### Collection Process
 
-Modules define prompts in `install-config.yaml`:
+Modules define prompts in `module.yaml`:
 
 ```yaml
 project_name:
@@ -218,12 +219,12 @@ Platform-specific content without source modification:
    src/modules/mymod/
    ├── _module-installer/
    │   ├── installer.js
-   │   └── install-config.yaml
+   ├── module.yaml
    ├── agents/
    └── tasks/
    ```
 
-2. **Configuration** (`install-config.yaml`)
+2. **Configuration** (`module.yaml`)
 
    ```yaml
    code: mymod

package/docs/web-bundles-gemini-gpt-guide.md

@@ -73,7 +73,7 @@ web-bundles/
 
 **Create a Gem:**
 
-1. Go to [Google AI Studio](https://aistudio.google.com/)
+1. Go to [Gemini Gem manager](https://gemini.google.com/gems/view)
 2. Click "New Gem" or "Create Gem"
 3. Give your Gem a name (e.g., "BMad PM Agent")
 4. **Enable "Code execution" for best results with document generation**

package/example-custom-content/README.md

@@ -2,3 +2,7 @@
 
 This is a demonstration of custom stand along agents and workflows. By having this content all in a folder with a custom.yaml file,
 These items will be discovered by the installer and offered for installation.
+
+This is how you could also create and share other custom agents and workflows not tied to a specific module.
+
+To see how these become installable, rename custom.bak -> custom.yaml and run the installer from the location you also have put this folder.

package/example-custom-content/agents/commit-poet/commit-poet.agent.yaml

@@ -1,6 +1,6 @@
 agent:
   metadata:
-    id: .bmad/agents/commit-poet/commit-poet.md
+    id: "{bmad_folder}/agents/commit-poet/commit-poet.md"
     name: "Inkwell Von Comitizen"
     title: "Commit Message Artisan"
     icon: "📜"

package/example-custom-content/agents/toolsmith/toolsmith-sidecar/instructions.md

@@ -41,7 +41,7 @@ CLI uses Commander.js, commands auto-loaded from `tools/cli/commands/`:
 ### Core Architecture Patterns
 
 1. **IDE Handlers**: Each IDE extends BaseIdeSetup class
-2. **Module Installers**: Modules can have `_module-installer/installer.js`
+2. **Module Installers**: Modules can have `module.yaml` and `_module-installer/installer.js`
 3. **Sub-modules**: IDE-specific customizations in `sub-modules/{ide-name}/`
 4. **Shared Utilities**: `tools/cli/installers/lib/ide/shared/` contains generators
 

package/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md

@@ -16,7 +16,7 @@
 - @/docs/v6-open-items.md - Known issues and open items
 - @/docs/document-sharding-guide.md - Guide for sharding large documents
 - @/docs/agent-customization-guide.md - How to customize agents
-- @/docs/custom-agent-installation.md - Custom agent installation guide
+- @/docs/custom-content-installation.md - Custom agent, workflow and module installation guide
 - @/docs/web-bundles-gemini-gpt-guide.md - Web bundle usage for AI platforms
 - @/docs/BUNDLE_DISTRIBUTION_SETUP.md - Bundle distribution setup
 

package/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md

@@ -117,7 +117,7 @@ Contains:
 
 - Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup
 - Fix installer bug: Check installer.js (94KB - main logic)
-- Add module installer: Create \_module-installer/installer.js in module
+- Add module installer: Create \_module-installer/installer.js if custom installer logic needed
 - Update shared generators: Modify files in /shared/ directory
 
 ## Relationships

package/example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md

@@ -27,7 +27,7 @@ src/modules/{module-name}/
 │       ├── injections.yaml
 │       ├── config.yaml
 │       └── sub-agents/
-├── install-config.yaml        # Module install configuration
+├── module.yaml        # Module install configuration
 └── README.md                  # Module documentation
 ```
 
@@ -145,7 +145,7 @@ Defined in @/tools/cli/lib/platform-codes.js
 - Create new module installer: Add \_module-installer/installer.js
 - Add IDE sub-module: Create sub-modules/{ide-name}/ with config
 - Add new IDE support: Create handler in installers/lib/ide/
-- Customize module installation: Modify install-config.yaml
+- Customize module installation: Modify module.yaml
 
 ## Relationships
 

package/example-custom-content/agents/toolsmith/toolsmith.agent.yaml

@@ -1,6 +1,6 @@
 agent:
   metadata:
-    id: custom/agents/toolsmith/toolsmith.md
+    id: "{bmad_folder}/agents/toolsmith/toolsmith.md"
     name: Vexor
     title: Infernal Toolsmith + Guardian of the BMAD Forge
     icon: ⚒️

package/example-custom-content/{custom.yaml → module.yaml}

@@ -1,3 +1,4 @@
 code: bmad-custom
 name: "BMAD-Custom: Sample Stand Alone Custom Agents and Workflows"
 default_selected: true
+type: custom

package/example-custom-content/workflows/quiz-master/steps/step-01-init.md

@@ -3,7 +3,7 @@ name: 'step-01-init'
 description: 'Initialize quiz game with mode selection and category choice'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01-init.md'
@@ -66,7 +66,7 @@ To set up the quiz game by selecting game mode, choosing a category, and prepari
 
 ### 1. Welcome and Configuration Loading
 
-Load config from {project-root}/.bmad/bmb/config.yaml to get user_name.
+Load config from {project-root}/{bmad_folder}/bmb/config.yaml to get user_name.
 
 Present dramatic welcome:
 "🎺 _DRAMATIC MUSIC PLAYS_ 🎺

package/example-custom-content/workflows/quiz-master/steps/step-02-q1.md

@@ -3,7 +3,7 @@ name: 'step-02-q1'
 description: 'Question 1 - Level 1 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-02-q1.md'

package/example-custom-content/workflows/quiz-master/steps/step-03-q2.md

@@ -3,7 +3,7 @@ name: 'step-03-q2'
 description: 'Question 2 - Level 2 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-q2.md'

package/example-custom-content/workflows/quiz-master/steps/step-04-q3.md

@@ -3,7 +3,7 @@ name: 'step-04-q3'
 description: 'Question 3 - Level 3 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-04-q3.md'

package/example-custom-content/workflows/quiz-master/steps/step-05-q4.md

@@ -3,7 +3,7 @@ name: 'step-05-q4'
 description: 'Question 4 - Level 4 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-05-q4.md'

package/example-custom-content/workflows/quiz-master/steps/step-06-q5.md

@@ -3,7 +3,7 @@ name: 'step-06-q5'
 description: 'Question 5 - Level 5 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-q5.md'

package/example-custom-content/workflows/quiz-master/steps/step-07-q6.md

@@ -3,7 +3,7 @@ name: 'step-07-q6'
 description: 'Question 6 - Level 6 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-07-q6.md'

package/example-custom-content/workflows/quiz-master/steps/step-08-q7.md

@@ -3,7 +3,7 @@ name: 'step-08-q7'
 description: 'Question 7 - Level 7 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-08-q7.md'

package/example-custom-content/workflows/quiz-master/steps/step-09-q8.md

@@ -3,7 +3,7 @@ name: 'step-09-q8'
 description: 'Question 8 - Level 8 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-09-q8.md'

package/example-custom-content/workflows/quiz-master/steps/step-10-q9.md

@@ -3,7 +3,7 @@ name: 'step-10-q9'
 description: 'Question 9 - Level 9 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-10-q9.md'

package/example-custom-content/workflows/quiz-master/steps/step-11-q10.md

@@ -3,7 +3,7 @@ name: 'step-11-q10'
 description: 'Question 10 - Level 10 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-11-q10.md'

package/example-custom-content/workflows/quiz-master/steps/step-12-results.md

@@ -3,7 +3,7 @@ name: 'step-12-results'
 description: 'Final results and celebration'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/{bmad_folder}/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-12-results.md'

package/example-custom-content/workflows/quiz-master/workflow.md

@@ -45,7 +45,7 @@ web_bundle: true
 
 ### 1. Module 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_folder}/bmb/config.yaml and resolve:
 
 - `user_name`, `output_folder`, `communication_language`, `document_output_language`
 

package/example-custom-module/mwm/README.md

@@ -2,3 +2,8 @@
 
 This module is an example and is not at all recommended for any usage, this module was not vetted by any medical professionals and should
 be considered at best for entertainment purposes only.
+
+You should see the option in the module selector when installing.
+
+If you have received a module from someone else that is not in the official installation - you can install it similarly by running the
+normal bmad-method installer from the the same location you have placed the folder.

package/example-custom-module/mwm/agents/cbt-coach/cbt-coach.agent.yaml

@@ -1,5 +1,6 @@
 agent:
   metadata:
+    id: "{bmad_folder}/mwm/agents/cbt-coach/cbt-coach.md"
     name: "Dr. Alexis, M.D."
     title: "CBT Coach"
     icon: "🧠"

package/example-custom-module/mwm/agents/crisis-navigator.agent.yaml

@@ -1,5 +1,6 @@
 agent:
   metadata:
+    id: "{bmad_folder}/mwm/agents/crisis-navigator.md"
     name: "Beacon"
     title: "Crisis Navigator"
     icon: "🆘"
@@ -95,7 +96,7 @@ agent:
       triggers:
         - trigger: party-mode
           input: SPM or fuzzy match start party mode
-          route: "{project-root}/.bmad/core/workflows/edit-agent/workflow.md"
+          route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
           data: crisis navigator agent discussion
           type: exec
         - trigger: expert-chat
@@ -117,7 +118,7 @@ agent:
           type: action
 
     - trigger: "safety-plan"
-      route: "{project-root}/.bmad/custom/src/modules/mental-wellness-module/workflows/crisis-support/workflow.md"
+      route: "{project-root}/{bmad_folder}/custom/src/modules/mental-wellness-module/workflows/crisis-support/workflow.md"
       description: "Create safety plan 🛡️"
       type: workflow
 

package/example-custom-module/mwm/agents/meditation-guide.agent.yaml

@@ -1,5 +1,6 @@
 agent:
   metadata:
+    id: "{bmad_folder}/mwm/agents/meditation-guide.md"
     name: "Serenity"
     title: "Meditation Guide"
     icon: "🧘"
@@ -92,7 +93,7 @@ agent:
       triggers:
         - trigger: party-mode
           input: SPM or fuzzy match start party mode
-          route: "{project-root}/.bmad/core/workflows/edit-agent/workflow.md"
+          route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
           data: meditation guide agent discussion
           type: exec
         - trigger: expert-chat
@@ -104,7 +105,7 @@ agent:
       triggers:
         - trigger: guided-meditation
           input: GM or fuzzy match guided meditation
-          route: "{project-root}/.bmad/custom/src/modules/mental-wellness-module/workflows/guided-meditation/workflow.md"
+          route: "{project-root}/{bmad_folder}/custom/src/modules/mental-wellness-module/workflows/guided-meditation/workflow.md"
           description: "Full meditation session 🧘"
           type: workflow
         - trigger: body-scan

package/example-custom-module/mwm/agents/wellness-companion/wellness-companion.agent.yaml

@@ -1,5 +1,6 @@
 agent:
   metadata:
+    id: "{bmad_folder}/mwm/agents/wellness-companion/wellness-companion.md"
     name: "Riley"
     title: "Wellness Companion"
     icon: "🌱"

package/example-custom-module/mwm/{_module-installer/install-config.yaml → module.yaml}

@@ -4,6 +4,7 @@
 code: mwm
 name: "MWM: Mental Wellness Module"
 default_selected: false
+type: module
 
 header: "MWM™: Custom Wellness Module"
 subheader: "Demo of Potential Non Coding Custom Module Use case"

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.14",
+  "version": "6.0.0-alpha.15",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/src/core/_module-installer/installer.js

@@ -6,7 +6,7 @@ const chalk = require('chalk');
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
+ * @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

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

@@ -8,7 +8,7 @@ const chalk = require('chalk');
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
+ * @param {Object} options.config - Module configuration from module.yaml
  * @param {Object} options.coreConfig - Core configuration containing user_name
  * @param {Array<string>} options.installedIDEs - Array of IDE codes that were installed
  * @param {Object} options.logger - Logger instance for output