ros/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-01-30 04:32:02 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
91f6c41be1509025f0c520adab856788ae7a4d0a
BMAD-METHOD/docs/_basement/reference/configuration/global-config.md
Alex Verkhovsky 91f6c41be1 docs: radical reduction of documentation scope for v6 beta (#1406) 
* docs: radical reduction of documentation scope for v6 beta

Archive and basement unreviewed content to ship a focused, minimal doc set.

Changes:
- Archive stale how-to workflow guides (will rewrite for v6)
- Archive outdated explanation and reference content
- Move unreviewed content to basement for later review
- Reorganize TEA docs into dedicated /tea/ section
- Add workflow-map visual reference page
- Simplify getting-started tutorial and sidebar navigation
- Add explanation pages: brainstorming, adversarial-review, party-mode,
  quick-flow, advanced-elicitation
- Fix base URL handling for subdirectory deployments (GitHub Pages forks)

The goal is a minimal, accurate doc set for beta rather than
comprehensive but potentially misleading content.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* refactor: restructure BMM and agents documentation by consolidating and flattening index files.

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-25 14:00:26 -06:00

1.1 KiB
Raw Blame History

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. :::