BMB module: skills not registered in .claude/skills/ and legacy config not read

[Chaadaev108]

Summary

Two issues discovered when using the BMB (BMad Builder) module installed via the BMAD installer (v6.2.1-next.20). The module files are correctly placed in _bmad/bmb/skills/, but the skills are not usable out of the box.

Environment

• BMAD version: 6.2.1-next.20 (installed 2026-03-22)
• Modules installed: BMM, BMB, WDS, TEA, Core
• Platform: Linux (WSL2), Claude Code CLI

Bug 1: BMB skills not registered in .claude/skills/

Expected behavior

After installation, BMB skills (bmad-agent-builder, bmad-workflow-builder, bmad-builder-setup) should be available as slash commands in Claude Code.

Actual behavior

Running /bmad-agent-builder returns Unknown skill: bmad-agent-builder. The installer places skill files in _bmad/bmb/skills/ but does not create corresponding entries in .claude/skills/.

Other modules (BMM, TEA, WDS, Core) have their skills correctly registered in .claude/skills/ — only BMB is missing.

Workaround

Manually create symlinks:

ln -s ../../_bmad/bmb/skills/bmad-agent-builder .claude/skills/bmad-agent-builder
ln -s ../../_bmad/bmb/skills/bmad-workflow-builder .claude/skills/bmad-workflow-builder
ln -s ../../_bmad/bmb/skills/bmad-builder-setup .claude/skills/bmad-builder-setup

After creating symlinks and restarting the terminal, all three skills work correctly.

Bug 2: BMB skills don't read legacy per-module configs → defaults to English

Expected behavior

bmad-agent-builder should detect communication_language: Русский from the existing configuration and communicate in the configured language.

Actual behavior

The agent greets in English: "Welcome! I'm your Agent Builder..."

Root cause: bmad-agent-builder (SKILL.md line 32) reads config from _bmad/config.yaml + _bmad/config.user.yaml (new unified format). But the installer writes configs in legacy per-module format: _bmad/core/config.yaml, _bmad/bmb/config.yaml, etc. Since the new-format files don't exist, communication_language is not found and the agent falls back to English.

Workaround

Run /bmad-builder-setup — it detects legacy configs, migrates them to the new unified format, and removes the old files:

• _bmad/core/config.yaml + _bmad/bmb/config.yaml → _bmad/config.yaml + _bmad/config.user.yaml

After migration and terminal restart, /bmad-agent-builder correctly greets in Russian and addresses the user by name.

Note: Other module configs (_bmad/bmm/config.yaml, _bmad/wds/config.yaml, _bmad/tea/config.yaml) remain in legacy format — their skills still read from per-module paths. These will need separate migration or the skills need fallback logic to check both locations.

Test Results

Step	Result
Fresh install, run /bmad-agent-builder	❌ Unknown skill
Create symlinks in .claude/skills/	✅ Skill recognized
Run /bmad-agent-builder (before config migration)	⚠️ Works but speaks English
Run /bmad-builder-setup (migrates legacy configs)	✅ Configs migrated
Run /bmad-agent-builder (after migration + terminal restart)	✅ Russian, addresses user by name

Suggested Fix

1. Installer: Register BMB skills in .claude/skills/ during installation (symlinks or copies, same as other modules)
2. BMB skills: Add fallback config resolution — if _bmad/config.yaml not found, check _bmad/core/config.yaml + _bmad/bmb/config.yaml (legacy paths). Or prompt the user to run /bmad-builder-setup

[coderabbitai]

🔗 Related PRs

#1735 - fix(installer): refuse install when ancestor dir has BMAD commands [merged]
#1841 - feat(skills): migrate all remaining platforms to native skills format [merged]
#1868 - refactor(skills): add SKILL.md entrypoint to skill directories [merged]
#2067 - fix: tea agent start [merged]
#2103 - fix(docs): correct skill names in getting-started tutorials [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[bmadcode]

thank you for pointing this out - fix incoming @Chaadaev108

[bmadcode]

Fixed in bmad-code-org/bmad-builder#73 — BMB skills (agent-builder, workflow-builder, module-builder) now fall back to _bmad/bmb/config.yaml when the unified config files don't exist, resolving config resolution with the legacy per-module format written by the installer.

Note: Bug 1 (skills not registered in .claude/skills/) is an installer issue tracked separately in bmad-code-org/BMAD-METHOD.

[bmadcode]

which is already merged in to fix.