Repository navigation
Precedence of bmad-customize #2368
Unanswered
skamalakaran-clgx
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
As per the bamd-customize documentation this is what provided
Priority 1 (wins): _bmad/custom/{skill-name}.user.toml (personal, gitignored)
Priority 2: _bmad/custom/{skill-name}.toml (team/org, committed)
Priority 3 (last): skill's own customize.toml (defaults)
If we have the org level standards, ARDs at bmad/custom/{skill-name}.toml (team/org, committed) level and if the developer can override it, then is it not a point of concern. Initially I thought we can use project-context.md for the Org standards. But seems it need to be focused at Project level not Org level. Then I came across bmad-customize and thought OK this is the right approach. But seems its not as developer version can override the org version. Not sure whether I am overlooking. My problem statement is how to impose org standards in BMAD. One option could be custom agents using BMAD Builder. Is there any other approach?
All reactions