* fix: bmad-help agent reads project docs and respects communication_language The help task fabricated tech stack information instead of reading actual project documentation (#1460) and ignored communication_language config (#1457). Three changes: 1. Step 2 now also extracts communication_language and project_knowledge from the active module's config.yaml 2. New step 3 scans project_knowledge path for documentation and uses discovered facts as grounding context, with anti-hallucination guard 3. Step 7 enforces {communication_language} in all output Chose inline config resolution over workflow.yaml conversion to match existing core task patterns (index-docs, shard-doc). Fixes #1460 Relates to #1457 * fix: clarify config extraction wording in help task 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. --------- Co-authored-by: Brian <bmadcode@gmail.com> |
||
|---|---|---|
| .. | ||
| _module-installer | ||
| agents | ||
| tasks | ||
| workflows | ||
| module-help.csv | ||
| module.yaml | ||