BMB workflows expect .agent.yaml files that don't exist in installed projects

[adambiggs]

Summary

BMB's edit and validate workflows prompt users to provide paths to .agent.yaml files, but the BMAD-METHOD installer (as of Beta.8) never copies .agent.yaml files into _bmad/. All agents are compiled to .md (XML-in-Markdown) during installation — the .agent.yaml source files are explicitly filtered out at multiple points in the install pipeline.

Details

What BMB expects

• workflow-edit-agent.md prompts: "Which agent would you like to edit? Please provide the path to the .agent.yaml file."
• workflow-validate-agent.md prompts: "Which agent would you like to validate? Please provide the path to the .agent.yaml file."

What actually exists in _bmad/

The installer compiles .agent.yaml → .md via tools/cli/lib/agent/compiler.js and writes only the compiled output. The .agent.yaml files are explicitly skipped during file copy in:

• copyCoreFiles() (installer.js)
• copyModuleWithFiltering() (manager.js)
• processAgentFiles() (installer.js)

The only .agent.yaml remnants are cached in _bmad/_config/custom/agents/ for reinstallation purposes, not at the paths BMB workflows expect.

Environment

• bmad-method: 6.0.0-Beta.8
• bmad-builder: v0.1.6

[coderabbitai]

🔗 Related PRs

#8 - feat: add file reference validator (MSSCI-14579) [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!