[BUG] bmad-brainstorming loads project_name from core/config.yaml, but project_name is owned by bmm

[blurb-jared-martin]

Summary

src/core-skills/bmad-brainstorming/workflow.md instructs the LLM to load project_name from _bmad/core/config.yaml, but project_name is defined by the bmm module — it lives in _bmad/bmm/config.yaml. On a fresh install, the key simply isn't present where brainstorming looks for it.

Expected

bmad-brainstorming loads config values from the correct per-module location(s) so project_name resolves on a standard install.

Actual

src/core-skills/bmad-brainstorming/workflow.md lines 35–37:

Load config from `{project-root}/_bmad/core/config.yaml` and resolve:

- `project_name`, `output_folder`, `user_name`
- `communication_language`, `document_output_language`, `user_skill_level`
- `date` as system-generated current datetime

On a 6.3.0 install, _bmad/core/config.yaml contains only:

user_name
communication_language
document_output_language
output_folder

project_name lives in _bmad/bmm/config.yaml, which is consistent with src/bmm-skills/module.yaml defining project_name as a bmm module variable (prompt: "What is your project called?"). src/core-skills/module.yaml does not define project_name.

The installer itself already knows this. In tools/installer/core/installer.js (around lines 1414–1415), its own config resolver looks up project_name in bmm/config.yaml. Only bmad-brainstorming's SKILL doc points at the wrong file.

Blast radius

Swept src/core-skills/* for skills that reference project_name. Only bmad-brainstorming has this mismatch. All bmm skills that need project_name (e.g., bmad-product-brief, bmad-agent-dev) correctly load from bmm/config.yaml.

Relevant paths

• Skill doc (wrong config path): src/core-skills/bmad-brainstorming/workflow.md:35
• Canonical home of project_name: src/bmm-skills/module.yaml + _bmad/bmm/config.yaml on install
• Installer's own resolver (correct behavior reference): tools/installer/core/installer.js lines ~1414–1415

Suggested fix

Change line 35 from {project-root}/_bmad/core/config.yaml to {project-root}/_bmad/bmm/config.yaml. A follow-up could split the load instruction so user_name/communication_language/output_folder come from core and project_name from bmm separately, since they genuinely live in different modules — but the one-line path fix is the immediate correctness fix.

PR incoming.

[coderabbitai]

🔗 Related PRs

#1769 - fix(templates): replace @ path prefixes with {project-root} [merged]
#1868 - refactor(skills): add SKILL.md entrypoint to skill directories [merged]
#2053 - fix: update src/core and src/bmm path references to match renamed directories [merged]
#2126 - fix: update bmb module-definition path [merged]
#2149 - fix: support skills/ folder as module source location [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!