From a23a9aa6240d6532f7564872b0ce2e1a6b0b78cd Mon Sep 17 00:00:00 2001 From: Michael Pursifull Date: Wed, 4 Feb 2026 19:57:26 -0600 Subject: [PATCH] fix: clarify config extraction wording in help task MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Remove "active module" reference from step 2 — config extraction happens during the all-modules scan, before module detection in step 4. Changed to "each scanned module's config" to match the existing iteration pattern. Addresses CodeRabbit review feedback on PR #1535. --- src/core/tasks/help.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/core/tasks/help.md b/src/core/tasks/help.md index cb577b0f8..c3c3fab11 100644 --- a/src/core/tasks/help.md +++ b/src/core/tasks/help.md @@ -54,7 +54,7 @@ Determine what was just completed: 1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv` -2. **Resolve output locations and config** — Scan each folder under `_bmad/` (except `_config`) for `config.yaml`. For each workflow row, resolve its `output-location` variables against that module's config so artifact paths can be searched. Also extract `communication_language` and `project_knowledge` from the active module's config. +2. **Resolve output locations and config** — Scan each folder under `_bmad/` (except `_config`) for `config.yaml`. For each workflow row, resolve its `output-location` variables against that module's config so artifact paths can be searched. Also extract `communication_language` and `project_knowledge` from each scanned module's config. 3. **Ground in project knowledge** — If `project_knowledge` resolves to an existing path, read available documentation files (architecture docs, project overview, tech stack references) for grounding context. Use discovered project facts when composing any project-specific output. Never fabricate project-specific details — if documentation is unavailable, state so.