mirror of
https://github.com/bmad-code-org/BMAD-METHOD.git
synced 2026-01-30 04:32:02 +00:00
Style Guide Additions: - Add Reference Structure section with 6 document types (Index, Catalog, Deep-Dive, Configuration, Glossary, Comprehensive) - Add Glossary Structure section with table-based format leveraging Starlight's right-nav for navigation - Include checklists for both new document types Reference Docs Updated: - agents/index.md: Catalog format, universal commands tip admonition - configuration/core-tasks.md: Configuration format with admonitions - configuration/global-config.md: Table-based config reference - workflows/index.md: Minimal index format - workflows/core-workflows.md: Catalog format - workflows/document-project.md: Deep-dive with Quick Facts admonition - workflows/bmgd-workflows.md: Comprehensive format, removed ~30 hr rules Glossary Rewritten: - Converted from 373 lines with ### headers to 123 lines with tables - Right nav now shows 9 categories instead of 50+ terms - Added italic context markers (*BMGD.*, *Brownfield.*, etc.) - Alphabetized terms within categories - Removed redundant inline TOC All Docs: - Remove horizontal rules (---) per style guide - Remove "Related" sections (sidebar handles navigation) - Standardize admonition usage - Archive deleted workflow customization docs Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
title
| title |
|---|
| Global Inheritable Config |
Configuration values defined in the Core Module that all other modules inherit by default.
Core Config Values
These values are set during installation and recorded to the core module.yaml:
| Config Key | Default | Description |
|---|---|---|
user_name |
System username | User's display name |
communication_language |
english |
Language for agent communication |
document_output_language |
english |
Language for generated documents |
output_folder |
_bmad-output |
Directory for workflow outputs |
Inheritance Behavior
All installed modules automatically clone these values into their own config. Modules can:
- Accept defaults — Use core values as-is (recommended)
- Override values — Replace with module-specific settings
- Extend values — Build on core values with additional paths
:::tip[Extending Config]
Use {output_folder} to reference the core value. Example: BMad Method defines planning_artifacts as {output_folder}/planning-artifacts, automatically inheriting whatever output folder the user configured.
:::