diff --git a/src/core/tasks/help.md b/src/core/tasks/help.md
index a2b414400..d0612c13c 100644
--- a/src/core/tasks/help.md
+++ b/src/core/tasks/help.md
@@ -35,13 +35,15 @@ Determine what was just completed:
 
 1. **Load catalog** — Load `{project-root}/_bmad/_config/bmad-help.csv`
 
-2. **Resolve output locations** — 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.
+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. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
+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 that clearly.
 
-4. **Detect active module** — Use MODULE DETECTION above to determine which module the user is working in.
+4. **Analyze input** — Task may provide a workflow name/code, conversational phrase, or nothing. Infer what was just completed using INPUT ANALYSIS above.
 
-5. **Present recommendations** — Show next steps based on completed workflows, phase/sequence ordering (KEY RULES), and artifact detection. Format per the following
+5. **Detect active module** — Use MODULE DETECTION above to determine which module the user is working in.
+
+6. **Present recommendations** — Show next steps based on completed workflows, phase/sequence ordering (KEY RULES), and artifact detection. Format per the following
 
 ## RECOMMENDED OUTPUT FORMAT
 
@@ -67,9 +69,10 @@ Determine what was just completed:
        - `Description: Create clear technical explanations with examples`
 
    ### Additional response output guidance to convey:
+   - Present all output in `{communication_language}` when available in module config
    - Run each workflow in a **fresh context window**
    - Load the agent using the platform's command format for `agent-command`, or run the workflow command directly
    - For **validation workflows**: recommend using a different high-quality LLM if available
    - For conversational requests: match the user's tone while presenting clearly
 
-6. Return to the calling process after presenting recommendations.
+7. Return to the calling process after presenting recommendations.
diff --git a/tools/cli/installers/lib/ide/templates/combined/kiro-workflow-yaml.md b/tools/cli/installers/lib/ide/templates/combined/kiro-workflow-yaml.md
index 33fadcc94..5204406cd 100644
--- a/tools/cli/installers/lib/ide/templates/combined/kiro-workflow-yaml.md
+++ b/tools/cli/installers/lib/ide/templates/combined/kiro-workflow-yaml.md
@@ -9,7 +9,7 @@ IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the c
 <steps CRITICAL="TRUE">
 1. Always LOAD the FULL #[[file:{{bmadFolderName}}/core/tasks/workflow.md]]
 2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config #[[file:{{bmadFolderName}}/{{path}}]]
-3. Pass the yaml path {{bmadFolderName}}/{{path}} as 'workflow-config' parameter to the workflow.md task instructions
+3. Pass the workflow path {{bmadFolderName}}/{{path}} as 'workflow-config' parameter to the workflow.md task instructions
 4. Follow workflow.md task instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>
diff --git a/tools/cli/installers/lib/modules/manager.js b/tools/cli/installers/lib/modules/manager.js
index fe36acbe1..508cdcf98 100644
--- a/tools/cli/installers/lib/modules/manager.js
+++ b/tools/cli/installers/lib/modules/manager.js
@@ -6,6 +6,7 @@ const { XmlHandler } = require('../../../lib/xml-handler');
 const { getProjectRoot, getSourcePath, getModulePath } = require('../../../lib/project-root');
 const { filterCustomizationData } = require('../../../lib/agent/compiler');
 const { ExternalModuleManager } = require('./external-manager');
+const { BMAD_FOLDER_NAME } = require('../ide/shared/path-utils');
 
 /**
  * Manages the installation, updating, and removal of BMAD modules.
@@ -26,7 +27,7 @@ const { ExternalModuleManager } = require('./external-manager');
 class ModuleManager {
   constructor(options = {}) {
     this.xmlHandler = new XmlHandler();
-    this.bmadFolderName = 'bmad'; // Default, can be overridden
+    this.bmadFolderName = BMAD_FOLDER_NAME; // Default, can be overridden
     this.customModulePaths = new Map(); // Initialize custom module paths
     this.externalModuleManager = new ExternalModuleManager(); // For external official modules
   }