_cfg -> _config

docs/agent-customization-guide.md

@@ -9,7 +9,7 @@ Customize BMad agents without modifying core files. All customizations persist t
 After installation, find agent customization files in:
 
 ```
-_bmad/_cfg/agents/
+_bmad/_config/agents/
 ├── core-bmad-master.customize.yaml
 ├── bmm-dev.customize.yaml
 ├── bmm-pm.customize.yaml
@@ -119,7 +119,7 @@ prompts:
 **Example 1: Customize Developer Agent for TDD**
 
 ```yaml
-# _bmad/_cfg/agents/bmm-dev.customize.yaml
+# _bmad/_config/agents/bmm-dev.customize.yaml
 agent:
   metadata:
     name: 'TDD Developer'
@@ -135,7 +135,7 @@ critical_actions:
 **Example 2: Add Custom Deployment Workflow**
 
 ```yaml
-# _bmad/_cfg/agents/bmm-dev.customize.yaml
+# _bmad/_config/agents/bmm-dev.customize.yaml
 menu:
   - trigger: deploy-staging
     workflow: '{project-root}/_bmad/deploy-staging.yaml'
@@ -148,7 +148,7 @@ menu:
 **Example 3: Multilingual Product Manager**
 
 ```yaml
-# _bmad/_cfg/agents/bmm-pm.customize.yaml
+# _bmad/_config/agents/bmm-pm.customize.yaml
 persona:
   role: 'Bilingual Product Manager'
   identity: 'Expert in US and LATAM markets'
@@ -166,15 +166,15 @@ memories:
 
 - **Start Small:** Customize one section at a time and rebuild to test
 - **Backup:** Copy customization files before major changes
-- **Update-Safe:** Your customizations in `_cfg/` survive all BMad updates
+- **Update-Safe:** Your customizations in `_config/` survive all BMad updates
 - **Per-Project:** Customization files are per-project, not global
-- **Version Control:** Consider committing `_cfg/` to share customizations with your team
+- **Version Control:** Consider committing `_config/` to share customizations with your team
 
 ## Module vs. Global Config
 
 **Module-Level (Recommended):**
 
-- Customize agents per-project in `_bmad/_cfg/agents/`
+- Customize agents per-project in `_bmad/_config/agents/`
 - Different projects can have different agent behaviors
 
 **Global Config (Coming Soon):**

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

@@ -28,7 +28,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor
 ```
 project-root/
 ├── _bmad/             # Centralized installation
-│   ├── _cfg/                  # Configuration
+│   ├── _config/                  # Configuration
 │   │   ├── agents/            # Agent configs
 │   │   └── agent-manifest.csv # Agent manifest
 │   ├── core/                  # Core module
@@ -265,7 +265,7 @@ Extractable config nodes:
 </agent>
 ```
 
-Generated in: `bmad/_cfg/agents/{module}-{agent}.md`
+Generated in: `bmad/_config/agents/{module}-{agent}.md`
 
 ## Troubleshooting
 
@@ -290,7 +290,7 @@ bmad status -v      # Detailed status
 ### Best Practices
 
 1. Run from project root
-2. Backup `_bmad/_cfg/` before updates
+2. Backup `_bmad/_config/` before updates
 3. Use interactive mode for guidance
 4. Review generated configs post-install
 

docs/v4-to-v6-upgrade.md

@@ -68,7 +68,7 @@ your-project/
     ├── bmm/             # BMad Method (software/game dev)
     ├── bmb/             # BMad Builder (create agents/workflows)
     ├── cis/             # Creative Intelligence Suite
-    └── _cfg/            # Your customizations
+    └── _config/            # Your customizations
         └── agents/      # Agent customization files
 ```
 
@@ -114,11 +114,11 @@ In v4, you may have modified agent files directly in `_bmad-*` folders.
 
 ### v6 Agent Customization
 
-**All customizations** now go in `_bmad/_cfg/agents/` using customize files:
+**All customizations** now go in `_bmad/_config/agents/` using customize files:
 
 **Example: Renaming an agent and changing communication style**
 
-File: `_bmad/_cfg/agents/bmm-pm.customize.yaml`
+File: `_bmad/_config/agents/bmm-pm.customize.yaml`
 
 ```yaml
 # Customize the PM agent
@@ -134,7 +134,7 @@ persona:
 **How it works:**
 
 - Base agent: `_bmad/bmm/agents/pm.md`
-- Customization: `_bmad/_cfg/agents/bmm-pm.customize.yaml`
+- Customization: `_bmad/_config/agents/bmm-pm.customize.yaml`
 - Result: Agent uses your custom name and style, but updates don't overwrite your changes
 
 ---
@@ -214,7 +214,7 @@ Since you are migrating an existing project from v4, it's most likely **Level 3
 - [ ] v4 folders backed up to `v4-backup/`
 - [ ] v6 installed to `_bmad/` folder
 - [ ] `workflow-init` run with correct project level selected
-- [ ] Agent customizations migrated to `_bmad/_cfg/agents/` if needed
+- [ ] Agent customizations migrated to `_bmad/_config/agents/` if needed
 - [ ] IDE integration working (test by listing agents)
 - [ ] For active development: `sprint-planning` workflow executed
 

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

@@ -336,7 +336,7 @@ Agents adapt their menus based on project phase and available workflows.
 
 Customize agents using the [Agent Customization Guide](./agent-customization-guide.md):
 
-1. Edit `_bmad/_cfg/agents/<agent>.customize.yaml`
+1. Edit `_bmad/_config/agents/<agent>.customize.yaml`
 2. Rebuild: `npx bmad-method build <agent-name>`
 3. Generate bundles: `npm run bundle`