feat: add bmad.config.yaml for team customization#4
Open
carlosleivacom wants to merge 2 commits intoErwanLorteau:devfrom
Open
feat: add bmad.config.yaml for team customization#4carlosleivacom wants to merge 2 commits intoErwanLorteau:devfrom
carlosleivacom wants to merge 2 commits intoErwanLorteau:devfrom
Conversation
Adds a lightweight config layer that lets teams customize agent personas and inject company context without forking the repo. New files: - bmad.config.example.yaml — documented example config with generic names - bmad.config.schema.json — JSON schema for IDE autocompletion - docs/configuration.md — full reference documentation - .gitignore — ignores bmad.config.yaml by convention Modified files: - workflow/orchestrator.md — Config Layer section with resolution rules - agents/product-manager.md — template placeholders as PoC - README.md — Team Customization section with quick start Backward compatible: no config file = current behavior unchanged.
Fixes all blocking and recommended issues from QA (Quinn #3514) and Docs (Maya #3515) review of PR ErwanLorteau#4 (config layer). Fix 1 (BLOCKER — both reviewers): - Correct 5 wrong defaults in Canonical Role Keys table: architect: James→Winston, developer: John→Amelia, qa-engineer: Mary/🔍→Quinn/🧪, tech-writer: ✍️→📚, ux-designer: Jane→Sally - Values now match actual agents/*.md H1 headers Fix 2 (Quinn — scope clarification): - Add Known Limitation row: only product-manager.md has H1 template placeholders in this PR; full coverage in follow-up Fix 3 (Maya — polish): - Add Config Discovery section (cross-ref to orchestrator.md) - Add company variable empty-string fallback note - Fix comma: warning message now reads correctly - Remove empty persona_append: from example.yaml - Move Team Customization before Credits in README - Add bmad.config.example.yaml copy reference in README - Clarify warn message in orchestrator.md with actionable text - Add explicit no-op rule for absent/empty persona_append
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the config layer described in #3.
Adds bmad.config.yaml support: a lightweight optional config file that lets teams
customize agent personas and inject company context without forking or modifying
framework files.
Changes
New files:
Modified files:
Backward Compatibility
No config file = zero behavior change. Every field is optional.
Closes #3