What is a good practice to keep files organized when using the BMAD method?

[pablohenneman]

Hey all,

I’m fairly new to BMAD and trying to become more structured in how I work with it across multiple projects. I’m running into some uncertainty around how BMAD is intended to be installed and how to organize files.

From experimenting and reading the docs, I understand that:

• BMAD installs a toolchain (agents, workflows, configs)
• Project state (workflow status, PRD, architecture, etc.) is stored in the project’s docs/ folder

What I’m unsure about is the recommended installation model:

• Should BMAD be installed in the root of every project repo?
  • This seems reliable for path resolution and keeps project state local
  • But it also means installing BMAD repeatedly and committing tool internals to each repo
• Or is it intended to be installed once (e.g. in a tools/ folder parallel to a projects/ folder), and then used from inside different project directories?
  • This feels cleaner conceptually, but I ran into path / discovery issues when trying this

I’d really appreciate hearing from more experienced users (or maintainers):

1. Where do you typically run npx bmad-method install?
2. Do you treat BMAD as project-local infrastructure or a shared tool?
3. What do you consider the “project root” / GitHub repo in a BMAD-based workflow?

Any examples of real-world folder layouts would be super helpful.

Thanks in advance!

[claudioweiler]

Hi!

Talking about v6 alpha that I testing..

I think that the framework may be used as a shared tool, but I think it was not design to work this way.

I've tried to install BMAD in a folder and tried to load agents in a subfolder, not worked, agents are not found. But if you add a symbolic link to BMAD folders it works, just note that I do simple tests, can't garante complete/functional "work".

[claudioweiler]

Just found this on sources:

https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmm/docs/enterprise-agentic-development.md#enterprise-configuration-with-git-submodules