From 9de0932e550627bbf04881ffae2b0afb4a46be01 Mon Sep 17 00:00:00 2001 From: Javier Gomez <113129149+Javierg9n4@users.noreply.github.com> Date: Wed, 10 Sep 2025 11:47:27 +0200 Subject: [PATCH] fix: update configuration file references from `bmad-core/core-config.yaml` to `.bmad-core/core-config.yaml` across multiple agent and task files for consistency and clarity. --- bmad-core/agents/analyst.md | 2 +- bmad-core/agents/architect.md | 2 +- bmad-core/agents/bmad-master.md | 2 +- bmad-core/agents/bmad-orchestrator.md | 4 ++-- bmad-core/agents/dev.md | 2 +- bmad-core/agents/pm.md | 2 +- bmad-core/agents/po.md | 2 +- bmad-core/agents/qa.md | 2 +- bmad-core/agents/sm.md | 2 +- bmad-core/agents/ux-expert.md | 2 +- bmad-core/data/bmad-kb.md | 2 +- bmad-core/tasks/apply-qa-fixes.md | 8 +++---- bmad-core/tasks/nfr-assess.md | 6 ++--- bmad-core/tasks/qa-gate.md | 4 ++-- bmad-core/tasks/review-story.md | 2 +- dist/agents/analyst.txt | 2 +- dist/agents/bmad-master.txt | 2 +- dist/agents/bmad-orchestrator.txt | 2 +- dist/agents/dev.txt | 8 +++---- dist/agents/qa.txt | 12 +++++----- .../agents/game-developer.txt | 4 ++-- .../teams/godot-game-team.txt | 8 +++---- dist/teams/team-all.txt | 22 +++++++++---------- dist/teams/team-fullstack.txt | 2 +- dist/teams/team-ide-minimal.txt | 22 +++++++++---------- dist/teams/team-no-ui.txt | 2 +- docs/user-guide.md | 2 +- .../agents/bmad-orchestrator.md | 2 +- .../tasks/apply-qa-fixes.md | 4 ++-- 29 files changed, 69 insertions(+), 69 deletions(-) diff --git a/bmad-core/agents/analyst.md b/bmad-core/agents/analyst.md index 6dea41c9..9b7bab59 100644 --- a/bmad-core/agents/analyst.md +++ b/bmad-core/agents/analyst.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task diff --git a/bmad-core/agents/architect.md b/bmad-core/agents/architect.md index 4814d59e..ab801f3f 100644 --- a/bmad-core/agents/architect.md +++ b/bmad-core/agents/architect.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task diff --git a/bmad-core/agents/bmad-master.md b/bmad-core/agents/bmad-master.md index 0e0cb9ee..ca2ed168 100644 --- a/bmad-core/agents/bmad-master.md +++ b/bmad-core/agents/bmad-master.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task diff --git a/bmad-core/agents/bmad-orchestrator.md b/bmad-core/agents/bmad-orchestrator.md index f4ed590a..afcd0873 100644 --- a/bmad-core/agents/bmad-orchestrator.md +++ b/bmad-core/agents/bmad-orchestrator.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task @@ -31,7 +31,7 @@ activation-instructions: - Assess user goal against available agents and workflows in this bundle - If clear match to an agent's expertise, suggest transformation with *agent command - If project-oriented, suggest *workflow-guidance to explore options - - Load resources only when needed - never pre-load (Exception: Read `bmad-core/core-config.yaml` during activation) + - Load resources only when needed - never pre-load (Exception: Read `.bmad-core/core-config.yaml` during activation) - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments. agent: name: BMad Orchestrator diff --git a/bmad-core/agents/dev.md b/bmad-core/agents/dev.md index 6362a303..3b275ab5 100644 --- a/bmad-core/agents/dev.md +++ b/bmad-core/agents/dev.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task diff --git a/bmad-core/agents/pm.md b/bmad-core/agents/pm.md index 1f8fc203..d6edd42d 100644 --- a/bmad-core/agents/pm.md +++ b/bmad-core/agents/pm.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task diff --git a/bmad-core/agents/po.md b/bmad-core/agents/po.md index a1c3be8b..a21c7868 100644 --- a/bmad-core/agents/po.md +++ b/bmad-core/agents/po.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task diff --git a/bmad-core/agents/qa.md b/bmad-core/agents/qa.md index 6d787635..b3c8a2ab 100644 --- a/bmad-core/agents/qa.md +++ b/bmad-core/agents/qa.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task diff --git a/bmad-core/agents/sm.md b/bmad-core/agents/sm.md index bca0c4f5..d642aba5 100644 --- a/bmad-core/agents/sm.md +++ b/bmad-core/agents/sm.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task diff --git a/bmad-core/agents/ux-expert.md b/bmad-core/agents/ux-expert.md index 47f36b23..f737ad06 100644 --- a/bmad-core/agents/ux-expert.md +++ b/bmad-core/agents/ux-expert.md @@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly ( activation-instructions: - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below - - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting + - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands - DO NOT: Load any other agent files during activation - ONLY load dependency files when user selects them for execution via command or request of a task diff --git a/bmad-core/data/bmad-kb.md b/bmad-core/data/bmad-kb.md index 47d5cb6c..9d0f4c30 100644 --- a/bmad-core/data/bmad-kb.md +++ b/bmad-core/data/bmad-kb.md @@ -181,7 +181,7 @@ npx bmad-method install ## Core Configuration (core-config.yaml) -**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. +**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. ### What is core-config.yaml? diff --git a/bmad-core/tasks/apply-qa-fixes.md b/bmad-core/tasks/apply-qa-fixes.md index ffbb9556..6af3037e 100644 --- a/bmad-core/tasks/apply-qa-fixes.md +++ b/bmad-core/tasks/apply-qa-fixes.md @@ -16,8 +16,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story. ```yaml required: - story_id: '{epic}.{story}' # e.g., "2.2" - - qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`) - - story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`) + - qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`) + - story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`) optional: - story_title: '{title}' # derive from story H1 if missing @@ -45,7 +45,7 @@ optional: ### 0) Load Core Config & Locate Story -- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root` +- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root` - Locate story file in `{story_root}/{epic}.{story}.*.md` - HALT if missing and ask for correct story id/path @@ -113,7 +113,7 @@ Status Rule: ## Blocking Conditions -- Missing `bmad-core/core-config.yaml` +- Missing `.bmad-core/core-config.yaml` - Story file not found for `story_id` - No QA artifacts found (neither gate nor assessments) - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list) diff --git a/bmad-core/tasks/nfr-assess.md b/bmad-core/tasks/nfr-assess.md index 337ef075..4566c2a6 100644 --- a/bmad-core/tasks/nfr-assess.md +++ b/bmad-core/tasks/nfr-assess.md @@ -9,11 +9,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit ```yaml required: - story_id: '{epic}.{story}' # e.g., "1.3" - - story_path: `bmad-core/core-config.yaml` for the `devStoryLocation` + - story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation` optional: - - architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile` - - technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences` + - architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile` + - technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences` - acceptance_criteria: From story file ``` diff --git a/bmad-core/tasks/qa-gate.md b/bmad-core/tasks/qa-gate.md index 446864c2..0f8a8ce5 100644 --- a/bmad-core/tasks/qa-gate.md +++ b/bmad-core/tasks/qa-gate.md @@ -16,7 +16,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision ## Gate File Location -**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates` +**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates` Slug rules: @@ -126,7 +126,7 @@ waiver: ## Output Requirements -1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml` +1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml` 2. **ALWAYS** append this exact format to story's QA Results section: ```text diff --git a/bmad-core/tasks/review-story.md b/bmad-core/tasks/review-story.md index 8360e443..2f6b2fbb 100644 --- a/bmad-core/tasks/review-story.md +++ b/bmad-core/tasks/review-story.md @@ -186,7 +186,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md **Template and Directory:** - Render from `../templates/qa-gate-tmpl.yaml` -- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing +- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing - Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml` Gate file structure: diff --git a/dist/agents/analyst.txt b/dist/agents/analyst.txt index 03be8d8b..322f9420 100644 --- a/dist/agents/analyst.txt +++ b/dist/agents/analyst.txt @@ -2230,7 +2230,7 @@ npx bmad-method install ## Core Configuration (core-config.yaml) -**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. +**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. ### What is core-config.yaml? diff --git a/dist/agents/bmad-master.txt b/dist/agents/bmad-master.txt index 101f1386..a0ffd1f4 100644 --- a/dist/agents/bmad-master.txt +++ b/dist/agents/bmad-master.txt @@ -7970,7 +7970,7 @@ npx bmad-method install ## Core Configuration (core-config.yaml) -**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. +**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. ### What is core-config.yaml? diff --git a/dist/agents/bmad-orchestrator.txt b/dist/agents/bmad-orchestrator.txt index 321ad11b..4e5c7f1d 100644 --- a/dist/agents/bmad-orchestrator.txt +++ b/dist/agents/bmad-orchestrator.txt @@ -653,7 +653,7 @@ npx bmad-method install ## Core Configuration (core-config.yaml) -**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. +**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. ### What is core-config.yaml? diff --git a/dist/agents/dev.txt b/dist/agents/dev.txt index f9fa4a2b..d423cde3 100644 --- a/dist/agents/dev.txt +++ b/dist/agents/dev.txt @@ -110,8 +110,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story. ```yaml required: - story_id: '{epic}.{story}' # e.g., "2.2" - - qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`) - - story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`) + - qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`) + - story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`) optional: - story_title: '{title}' # derive from story H1 if missing @@ -139,7 +139,7 @@ optional: ### 0) Load Core Config & Locate Story -- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root` +- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root` - Locate story file in `{story_root}/{epic}.{story}.*.md` - HALT if missing and ask for correct story id/path @@ -207,7 +207,7 @@ Status Rule: ## Blocking Conditions -- Missing `bmad-core/core-config.yaml` +- Missing `.bmad-core/core-config.yaml` - Story file not found for `story_id` - No QA artifacts found (neither gate nor assessments) - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list) diff --git a/dist/agents/qa.txt b/dist/agents/qa.txt index 0979397c..0fcbc323 100644 --- a/dist/agents/qa.txt +++ b/dist/agents/qa.txt @@ -121,11 +121,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit ```yaml required: - story_id: '{epic}.{story}' # e.g., "1.3" - - story_path: `bmad-core/core-config.yaml` for the `devStoryLocation` + - story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation` optional: - - architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile` - - technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences` + - architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile` + - technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences` - acceptance_criteria: From story file ``` @@ -475,7 +475,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision ## Gate File Location -**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates` +**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates` Slug rules: @@ -585,7 +585,7 @@ waiver: ## Output Requirements -1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml` +1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml` 2. **ALWAYS** append this exact format to story's QA Results section: ```text @@ -810,7 +810,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md **Template and Directory:** - Render from `../templates/qa-gate-tmpl.yaml` -- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing +- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing - Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml` Gate file structure: diff --git a/dist/expansion-packs/bmad-godot-game-dev/agents/game-developer.txt b/dist/expansion-packs/bmad-godot-game-dev/agents/game-developer.txt index 6839d2ed..a9a24840 100644 --- a/dist/expansion-packs/bmad-godot-game-dev/agents/game-developer.txt +++ b/dist/expansion-packs/bmad-godot-game-dev/agents/game-developer.txt @@ -286,7 +286,7 @@ optional: ### 0) Load Core Config & Locate Story -- Read `bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root` +- Read `.bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root` - Locate story file in `{story_root}/{epic}.{story}.*.md` - HALT if missing and ask for correct story id/path @@ -386,7 +386,7 @@ Status Rule: ## Blocking Conditions -- Missing `bmad-core/core-config.yaml` +- Missing `.bmad-core/core-config.yaml` - Story file not found for `story_id` - No QA artifacts found (neither gate nor assessments) - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list) diff --git a/dist/expansion-packs/bmad-godot-game-dev/teams/godot-game-team.txt b/dist/expansion-packs/bmad-godot-game-dev/teams/godot-game-team.txt index 17a2a233..8f34244f 100644 --- a/dist/expansion-packs/bmad-godot-game-dev/teams/godot-game-team.txt +++ b/dist/expansion-packs/bmad-godot-game-dev/teams/godot-game-team.txt @@ -8943,7 +8943,7 @@ optional: ### 0) Load Core Config & Locate Story -- Read `bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root` +- Read `.bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root` - Locate story file in `{story_root}/{epic}.{story}.*.md` - HALT if missing and ask for correct story id/path @@ -9043,7 +9043,7 @@ Status Rule: ## Blocking Conditions -- Missing `bmad-core/core-config.yaml` +- Missing `.bmad-core/core-config.yaml` - Story file not found for `story_id` - No QA artifacts found (neither gate nor assessments) - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list) @@ -19903,7 +19903,7 @@ optional: ### 0) Load Core Config & Locate Story -- Read `bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root` +- Read `.bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root` - Locate story file in `{story_root}/{epic}.{story}.*.md` - HALT if missing and ask for correct story id/path @@ -20003,7 +20003,7 @@ Status Rule: ## Blocking Conditions -- Missing `bmad-core/core-config.yaml` +- Missing `.bmad-core/core-config.yaml` - Story file not found for `story_id` - No QA artifacts found (neither gate nor assessments) - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list) diff --git a/dist/teams/team-all.txt b/dist/teams/team-all.txt index db88f523..4e31c743 100644 --- a/dist/teams/team-all.txt +++ b/dist/teams/team-all.txt @@ -1141,7 +1141,7 @@ npx bmad-method install ## Core Configuration (core-config.yaml) -**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. +**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. ### What is core-config.yaml? @@ -6499,8 +6499,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story. ```yaml required: - story_id: '{epic}.{story}' # e.g., "2.2" - - qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`) - - story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`) + - qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`) + - story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`) optional: - story_title: '{title}' # derive from story H1 if missing @@ -6528,7 +6528,7 @@ optional: ### 0) Load Core Config & Locate Story -- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root` +- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root` - Locate story file in `{story_root}/{epic}.{story}.*.md` - HALT if missing and ask for correct story id/path @@ -6596,7 +6596,7 @@ Status Rule: ## Blocking Conditions -- Missing `bmad-core/core-config.yaml` +- Missing `.bmad-core/core-config.yaml` - Story file not found for `story_id` - No QA artifacts found (neither gate nor assessments) - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list) @@ -9085,11 +9085,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit ```yaml required: - story_id: '{epic}.{story}' # e.g., "1.3" - - story_path: `bmad-core/core-config.yaml` for the `devStoryLocation` + - story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation` optional: - - architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile` - - technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences` + - architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile` + - technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences` - acceptance_criteria: From story file ``` @@ -9439,7 +9439,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision ## Gate File Location -**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates` +**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates` Slug rules: @@ -9549,7 +9549,7 @@ waiver: ## Output Requirements -1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml` +1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml` 2. **ALWAYS** append this exact format to story's QA Results section: ```text @@ -9774,7 +9774,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md **Template and Directory:** - Render from `../templates/qa-gate-tmpl.yaml` -- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing +- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing - Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml` Gate file structure: diff --git a/dist/teams/team-fullstack.txt b/dist/teams/team-fullstack.txt index 4f389def..f85754de 100644 --- a/dist/teams/team-fullstack.txt +++ b/dist/teams/team-fullstack.txt @@ -976,7 +976,7 @@ npx bmad-method install ## Core Configuration (core-config.yaml) -**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. +**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. ### What is core-config.yaml? diff --git a/dist/teams/team-ide-minimal.txt b/dist/teams/team-ide-minimal.txt index e3683d68..51d600d7 100644 --- a/dist/teams/team-ide-minimal.txt +++ b/dist/teams/team-ide-minimal.txt @@ -895,7 +895,7 @@ npx bmad-method install ## Core Configuration (core-config.yaml) -**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. +**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. ### What is core-config.yaml? @@ -3299,8 +3299,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story. ```yaml required: - story_id: '{epic}.{story}' # e.g., "2.2" - - qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`) - - story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`) + - qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`) + - story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`) optional: - story_title: '{title}' # derive from story H1 if missing @@ -3328,7 +3328,7 @@ optional: ### 0) Load Core Config & Locate Story -- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root` +- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root` - Locate story file in `{story_root}/{epic}.{story}.*.md` - HALT if missing and ask for correct story id/path @@ -3396,7 +3396,7 @@ Status Rule: ## Blocking Conditions -- Missing `bmad-core/core-config.yaml` +- Missing `.bmad-core/core-config.yaml` - Story file not found for `story_id` - No QA artifacts found (neither gate nor assessments) - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list) @@ -3542,11 +3542,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit ```yaml required: - story_id: '{epic}.{story}' # e.g., "1.3" - - story_path: `bmad-core/core-config.yaml` for the `devStoryLocation` + - story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation` optional: - - architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile` - - technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences` + - architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile` + - technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences` - acceptance_criteria: From story file ``` @@ -3896,7 +3896,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision ## Gate File Location -**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates` +**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates` Slug rules: @@ -4006,7 +4006,7 @@ waiver: ## Output Requirements -1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml` +1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml` 2. **ALWAYS** append this exact format to story's QA Results section: ```text @@ -4231,7 +4231,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md **Template and Directory:** - Render from `../templates/qa-gate-tmpl.yaml` -- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing +- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing - Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml` Gate file structure: diff --git a/dist/teams/team-no-ui.txt b/dist/teams/team-no-ui.txt index 0bf562e8..57d9a790 100644 --- a/dist/teams/team-no-ui.txt +++ b/dist/teams/team-no-ui.txt @@ -922,7 +922,7 @@ npx bmad-method install ## Core Configuration (core-config.yaml) -**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. +**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility. ### What is core-config.yaml? diff --git a/docs/user-guide.md b/docs/user-guide.md index 117b08b4..65cba22b 100644 --- a/docs/user-guide.md +++ b/docs/user-guide.md @@ -501,7 +501,7 @@ When creating custom web bundles or uploading to AI platforms, include your `tec ## Core Configuration -The `bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml. +The `.bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml. ### Developer Context Files diff --git a/expansion-packs/bmad-godot-game-dev/agents/bmad-orchestrator.md b/expansion-packs/bmad-godot-game-dev/agents/bmad-orchestrator.md index de8e469f..e5b8a363 100644 --- a/expansion-packs/bmad-godot-game-dev/agents/bmad-orchestrator.md +++ b/expansion-packs/bmad-godot-game-dev/agents/bmad-orchestrator.md @@ -31,7 +31,7 @@ activation-instructions: - Assess user goal against available agents and workflows in this bundle - If clear match to an agent's expertise, suggest transformation with *agent command - If project-oriented, suggest *workflow-guidance to explore options - - Load resources only when needed - never pre-load (Exception: Read `bmad-core/core-config.yaml` during activation) + - Load resources only when needed - never pre-load (Exception: Read `.bmad-core/core-config.yaml` during activation) - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments. agent: name: BMad Orchestrator diff --git a/expansion-packs/bmad-godot-game-dev/tasks/apply-qa-fixes.md b/expansion-packs/bmad-godot-game-dev/tasks/apply-qa-fixes.md index 683dfa42..463ea0bf 100644 --- a/expansion-packs/bmad-godot-game-dev/tasks/apply-qa-fixes.md +++ b/expansion-packs/bmad-godot-game-dev/tasks/apply-qa-fixes.md @@ -50,7 +50,7 @@ optional: ### 0) Load Core Config & Locate Story -- Read `bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root` +- Read `.bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root` - Locate story file in `{story_root}/{epic}.{story}.*.md` - HALT if missing and ask for correct story id/path @@ -150,7 +150,7 @@ Status Rule: ## Blocking Conditions -- Missing `bmad-core/core-config.yaml` +- Missing `.bmad-core/core-config.yaml` - Story file not found for `story_id` - No QA artifacts found (neither gate nor assessments) - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)