Merge 6522e8e92a into 1677d54f22

docs/how-to/install-bmad.md

@@ -57,24 +57,9 @@ Each tool has its own way of integrating commands. The installer creates tiny pr
 
 The installer shows available modules. Select whichever ones you need — most users just want **BMad Method** (the software development module).
 
-### 5. Configure Settings
+### 5. Follow the Prompts
 
-The installer prompts you for core settings that control how agents behave:
+The installer guides you through the rest — custom content, settings, etc.
-
-| Setting | Default | Description |
-| ------- | ------- | ----------- |
-| **User Name** | `BMad` | What agents call you — use your name or a team name |
-| **Communication Language** | `English` | Language agents use when chatting with you |
-| **Document Output Language** | `English` | Language for generated documents and artifacts |
-| **Output Folder** | `_bmad-output` | Where agents save generated files |
-| **Interaction Style** | `structured` | How agents ask you questions (see below) |
-
-**Interaction Style** controls how agents present choices:
-
-- **Structured** (recommended) — Agents present numbered option lists for every question, using your IDE's native question tool when available. This keeps conversations focused and reduces ambiguity.
-- **Open** — Agents ask natural conversational questions. More flexible but can lead to longer back-and-forth.
-
-These settings are saved to `_bmad/<module>/config.yaml` and can be changed later by editing that file and rerunning the installer.
 
 ## What You Get
 

src/core/module-help.csv

@@ -7,4 +7,3 @@ core,anytime,Shard Document,SD,,_bmad/core/tasks/shard-doc.xml,bmad-shard-doc,fa
 core,anytime,Editorial Review - Prose,EP,,_bmad/core/tasks/editorial-review-prose.xml,bmad-editorial-review-prose,false,,,"Review prose for clarity, tone, and communication issues. Use after drafting to polish written content.",report located with target document,"three-column markdown table with suggested fixes",
 core,anytime,Editorial Review - Structure,ES,,_bmad/core/tasks/editorial-review-structure.xml,bmad-editorial-review-structure,false,,,"Propose cuts, reorganization, and simplification while preserving comprehension. Use when doc produced from multiple subprocesses or needs structural improvement.",report located with target document,
 core,anytime,Adversarial Review (General),AR,,_bmad/core/tasks/review-adversarial-general.xml,bmad-review-adversarial-general,false,,,"Review content critically to find issues and weaknesses. Use for quality assurance or before finalizing deliverables. Code Review in other modules run this automatically, but its useful also for document reviews",,
-core,anytime,Edge Case Hunter Review,ECH,,_bmad/core/tasks/review-edge-case-hunter.xml,bmad-review-edge-case-hunter,false,,,"Walk every branching path and boundary condition in code, report only unhandled edge cases. Use alongside adversarial review for orthogonal coverage - method-driven not attitude-driven.",,

src/core/module.yaml

@@ -26,10 +26,10 @@ output_folder:
 
 interaction_style:
   prompt: "How should agents ask you questions?"
-  default: "open"
+  default: "structured"
   result: "{value}"
   single-select:
-    - value: "open"
-      label: "Open - Natural conversational questions (recommended)"
     - value: "structured"
-      label: "Structured - Numbered option lists"
+      label: "Structured - Numbered option lists (recommended)"
+    - value: "open"
+      label: "Open - Natural conversational questions"

src/core/tasks/review-edge-case-hunter.xml

@@ -1,64 +0,0 @@
-<!-- if possible, run this in a separate subagent or process with read access to the project,
-  but no context except the content to review -->
-
-<task id="_bmad/core/tasks/review-edge-case-hunter.xml" name="Edge Case Hunter Review"
-  description="Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven.">
-  <objective>You are a pure path tracer. Never comment on whether code is good or bad; only list missing handling.
-When a diff is provided, scan only the diff hunks and list boundaries that are directly reachable from the changed lines and lack an explicit guard in the diff.
-When no diff is provided (full file or function), treat the entire provided content as the scope.
-Ignore the rest of the codebase unless the provided content explicitly references external functions.</objective>
-
-  <inputs>
-    <input name="content" desc="Content to review - diff, full file, or function" />
-    <input name="also_consider" required="false"
-      desc="Optional areas to keep in mind during review alongside normal edge-case analysis" />
-  </inputs>
-
-  <output-format>Return ONLY a valid JSON array of objects. Each object must contain exactly these four fields and nothing else:
-{
-  "location": "file:line",
-  "trigger_condition": "one-line description (max 15 words)",
-  "guard_snippet": "minimal code sketch that closes the gap",
-  "potential_consequence": "what could actually go wrong (max 15 words)"
-}
-No extra text, no explanations, no markdown wrapping.</output-format>
-
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-
-    <i>Your method is exhaustive path enumeration — mechanically walk every branch, not hunt by intuition</i>
-    <i>Trace each branching path: conditionals, switches, early returns, guard clauses, loops, error handlers</i>
-    <i>Trace each boundary condition: null, undefined, empty, zero, negative, overflow, max-length, type coercion, concurrency, timing</i>
-    <i>Report ONLY paths and conditions that lack handling — discard handled ones silently</i>
-    <i>Do NOT editorialize or add filler — findings only</i>
-  </llm>
-
-  <flow>
-    <step n="1" title="Receive Content">
-      <action>Load the content to review from provided input or context</action>
-      <action>If content to review is empty, ask for clarification and abort task</action>
-      <action>Identify content type (diff, full file, or function) to determine scope rules</action>
-    </step>
-
-    <step n="2" title="Exhaustive Path Analysis" critical="true">
-      <mandate>Walk every branching path and boundary condition within scope - report only unhandled ones</mandate>
-      <action>If also_consider input was provided, incorporate those areas into the analysis</action>
-      <action>Enumerate all branching paths and boundary conditions within scope: conditionals, switches, early returns, guard clauses, loops, error handlers, null/empty states, overflow, type edges, concurrency, timing</action>
-      <action>For each path: determine whether the content handles it</action>
-      <action>Collect only the unhandled paths as findings - discard handled ones silently</action>
-    </step>
-
-    <step n="3" title="Present Findings">
-      <action>Output findings as a JSON array following the output-format specification exactly</action>
-    </step>
-  </flow>
-
-  <halt-conditions>
-    <condition>HALT if zero findings - this is suspicious, re-analyze or ask for guidance</condition>
-    <condition>HALT if content is empty or unreadable</condition>
-  </halt-conditions>
-
-</task>

src/core/tasks/workflow.xml

@@ -2,7 +2,6 @@
   <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
 
   <llm critical="true">
-    <mandate>RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use the native question tool. No exceptions. No inline prompts. When {interaction_style} is "open", ask questions naturally in conversation. If you cannot determine {interaction_style}, default to open mode.</mandate>
     <mandate>Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files</mandate>
     <mandate>Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown</mandate>
     <mandate>Execute ALL steps in instructions IN EXACT ORDER</mandate>

src/utility/agent-components/activation-rules.txt

@@ -1,6 +1,5 @@
   <rules>
     <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
-    <r>Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.</r>
     <r> Stay in character until exit selected</r>
     <r> Display Menu items as the item dictates and in the order given.</r>
     <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>

src/utility/agent-components/activation-steps.txt

@@ -1,7 +1,7 @@
     <step n="1">Load persona from this current agent file (already in context)</step>
     <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
         - Load and read {project-root}/_bmad/{{module}}/config.yaml NOW
-        - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}, {interaction_style}, {document_output_language}
+        - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}, {interaction_style}
         - VERIFY: If config not loaded, STOP and report error to user
         - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
     </step>

src/utility/agent-components/agent-command-header.md

@@ -1,3 +1 @@
 You must fully embody this agent's persona and follow all activation instructions, steps and rules exactly as specified. NEVER break character until given an exit command.
-
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions. If you cannot determine {interaction_style}, default to open mode.

src/utility/agent-components/handler-action.txt

@@ -1,5 +1,4 @@
   <handler type="action">
     When menu item has: action="#id" → Find prompt with id="id" in current agent XML, follow its content
     When menu item has: action="text" → Follow the text directly as an inline instruction
-    RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", ALL questions to the user MUST use the AskUserQuestion tool. No plain text prompts. If you cannot determine {interaction_style}, default to open mode.
   </handler>

src/utility/agent-components/handler-exec.txt

@@ -3,5 +3,4 @@
       1. Read fully and follow the file at that path
       2. Process the complete file and follow all instructions within it
       3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
-      4. RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", ALL questions to the user MUST use the AskUserQuestion tool. No plain text prompts. If you cannot determine {interaction_style}, default to open mode.
     </handler>

src/utility/agent-components/handler-multi.txt

@@ -10,5 +10,5 @@
             - For workflow="path/to/workflow.yaml": follow the `handler type="workflow"` instructions
             - For action="...": Perform the specified action directly
          5. Support both exact matches and fuzzy matching based on the match attribute
-         6. If no handler matches, prompt user to choose from available options using the AskUserQuestion tool when interaction_style is "structured"
+         6. If no handler matches, prompt user to choose from available options
       </handler>

src/utility/agent-components/handler-validate-workflow.txt

@@ -3,5 +3,5 @@
         1. You MUST LOAD the file at: {project-root}/_bmad/core/tasks/validate-workflow.xml
         2. READ its entire contents and EXECUTE all instructions in that file
         3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
-        4. The workflow should try to identify the file to validate based on checklist context or else ask the user to specify using the AskUserQuestion tool when interaction_style is "structured"
+        4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
     </handler>

src/utility/agent-components/handler-workflow.txt

@@ -7,5 +7,4 @@
       4. Follow workflow.xml instructions precisely following all steps
       5. Save outputs after completing EACH workflow step (never batch multiple steps together)
       6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-      7. RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", ALL questions to the user MUST use the AskUserQuestion tool. No plain text prompts. If you cannot determine {interaction_style}, default to open mode.
     </handler>

tools/cli/installers/lib/ide/codex.js

@@ -416,7 +416,6 @@ class CodexSetup extends BaseIdeSetup {
     const skillContent =
       `---\n${fm}\n---\n` +
       "\nYou must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.\n" +
-      '\nRULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `ask_user_question` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.\n' +
       '\n<agent-activation CRITICAL="TRUE">\n' +
       `1. LOAD the FULL agent file from @${agentPath}\n` +
       '2. READ its entire contents - this contains the complete agent persona, menu, and instructions\n' +

tools/cli/installers/lib/ide/platform-codes.yaml

@@ -39,7 +39,7 @@ platforms:
     description: "Anthropic's official CLI for Claude"
     installer:
       target_dir: .claude/commands
-      template_type: claude
+      template_type: default
       ancestor_conflict_check: true
 
   cline:

tools/cli/installers/lib/ide/templates/agent-command-template.md

@@ -5,7 +5,7 @@ description: '{{description}}'
 
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. Do NOT ask open-ended inline questions. No exceptions.
 
 <agent-activation CRITICAL="TRUE">
 1. LOAD the FULL agent file from @_bmad/{{module}}/agents/{{path}}

tools/cli/installers/lib/ide/templates/combined/antigravity.md

@@ -3,8 +3,8 @@ name: '{{name}}'
 description: '{{description}}'
 ---
 
-Read the entire workflow file at: {project-root}/{{bmadFolderName}}/{{workflow_path}}
+Read the entire workflow file at: {project-root}/_bmad/{{workflow_path}}
 
 Follow all instructions in the workflow file exactly as written.
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.

tools/cli/installers/lib/ide/templates/combined/claude-agent.md

@@ -1,17 +0,0 @@
----
-name: '{{name}}'
-description: '{{description}}'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `AskUserQuestion` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/{{bmadFolderName}}/{{path}}
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. FOLLOW every step in the <activation> section precisely
-4. DISPLAY the welcome/greeting as instructed
-5. PRESENT the numbered menu
-6. WAIT for user input before proceeding
-</agent-activation>

tools/cli/installers/lib/ide/templates/combined/claude-agent.md

@@ -0,0 +1 @@
+default-agent.md

tools/cli/installers/lib/ide/templates/combined/claude-task.md

@@ -1,12 +0,0 @@
----
-name: '{{name}}'
-description: '{{description}}'
----
-
-# {{name}}
-
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `AskUserQuestion` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
-
-Read the entire task file at: {project-root}/{{bmadFolderName}}/{{path}}
-
-Follow all instructions in the task file exactly as written.

tools/cli/installers/lib/ide/templates/combined/claude-tool.md

@@ -1,12 +0,0 @@
----
-name: '{{name}}'
-description: '{{description}}'
----
-
-# {{name}}
-
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `AskUserQuestion` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
-
-Read the entire tool file at: {project-root}/{{bmadFolderName}}/{{path}}
-
-Follow all instructions in the tool file exactly as written.

tools/cli/installers/lib/ide/templates/combined/claude-workflow-yaml.md

@@ -1,16 +0,0 @@
----
-name: '{{name}}'
-description: '{{description}}'
----
-
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `AskUserQuestion` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/{{bmadFolderName}}/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/{{bmadFolderName}}/{{path}}
-3. Pass the yaml path @{project-root}/{{bmadFolderName}}/{{path}} as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml 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>

tools/cli/installers/lib/ide/templates/combined/claude-workflow-yaml.md

@@ -0,0 +1 @@
+default-workflow-yaml.md

tools/cli/installers/lib/ide/templates/combined/claude-workflow.md

@@ -1,8 +0,0 @@
----
-name: '{{name}}'
-description: '{{description}}'
----
-
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `AskUserQuestion` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/{{bmadFolderName}}/{{path}}, READ its entire contents and follow its directions exactly!

tools/cli/installers/lib/ide/templates/combined/claude-workflow.md

@@ -0,0 +1 @@
+default-workflow.md

tools/cli/installers/lib/ide/templates/combined/default-agent.md

@@ -5,10 +5,10 @@ description: '{{description}}'
 
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions.
 
 <agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from {project-root}/{{bmadFolderName}}/{{path}}
+1. LOAD the FULL agent file from {project-root}/_bmad/{{path}}
 2. READ its entire contents - this contains the complete agent persona, menu, and instructions
 3. FOLLOW every step in the <activation> section precisely
 4. DISPLAY the welcome/greeting as instructed

tools/cli/installers/lib/ide/templates/combined/default-task.md

@@ -5,8 +5,8 @@ description: '{{description}}'
 
 # {{name}}
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
-
 Read the entire task file at: {project-root}/{{bmadFolderName}}/{{path}}
 
 Follow all instructions in the task file exactly as written.
+
+RULE: When interaction_style is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions.

tools/cli/installers/lib/ide/templates/combined/default-tool.md

@@ -5,8 +5,8 @@ description: '{{description}}'
 
 # {{name}}
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
-
 Read the entire tool file at: {project-root}/{{bmadFolderName}}/{{path}}
 
 Follow all instructions in the tool file exactly as written.
+
+RULE: When interaction_style is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions.

tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md

@@ -3,7 +3,7 @@ name: '{{name}}'
 description: '{{description}}'
 ---
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions.
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 

tools/cli/installers/lib/ide/templates/combined/default-workflow.md

@@ -3,6 +3,6 @@ name: '{{name}}'
 description: '{{description}}'
 ---
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST call the AskUserQuestion tool. Do NOT write questions as plain text. No exceptions.
 
 IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/{{bmadFolderName}}/{{path}}, READ its entire contents and follow its directions exactly!

tools/cli/installers/lib/ide/templates/combined/gemini-agent.toml

@@ -6,9 +6,8 @@ PRE-FLIGHT CHECKLIST:
 1.  [ ] IMMEDIATE ACTION: Load and parse {project-root}/{{bmadFolderName}}/{{module}}/config.yaml - store ALL config values in memory for use throughout the session.
 2.  [ ] IMMEDIATE ACTION: Read and internalize the full agent definition at {project-root}/{{bmadFolderName}}/{{path}}.
 3.  [ ] CONFIRM: The user's name from config is {user_name}.
-4.  [ ] CONFIRM: interaction_style is set to "{interaction_style}".
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
 
 Only after all checks are complete, greet the user by name and display the menu.
 Acknowledge this checklist is complete in your first response.

tools/cli/installers/lib/ide/templates/combined/gemini-task.toml

@@ -6,8 +6,7 @@ TASK INSTRUCTIONS:
 1. LOAD the task file from {project-root}/{{bmadFolderName}}/{{path}}
 2. READ its entire contents
 3. FOLLOW every instruction precisely as specified
-
+4. RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
 
 TASK FILE: {project-root}/{{bmadFolderName}}/{{path}}
 """

tools/cli/installers/lib/ide/templates/combined/gemini-tool.toml

@@ -6,8 +6,7 @@ TOOL INSTRUCTIONS:
 1. LOAD the tool file from {project-root}/{{bmadFolderName}}/{{path}}
 2. READ its entire contents
 3. FOLLOW every instruction precisely as specified
-
+4. RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
 
 TOOL FILE: {project-root}/{{bmadFolderName}}/{{path}}
 """

tools/cli/installers/lib/ide/templates/combined/gemini-workflow-yaml.toml

@@ -11,8 +11,7 @@ CRITICAL: This is a structured YAML workflow. Follow these steps precisely:
    - Dependencies between steps
 3. EXECUTE each step in order
 4. VALIDATE outputs before proceeding to next step
-
+5. RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
 
 WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{workflow_path}}
 """

tools/cli/installers/lib/ide/templates/combined/gemini-workflow.toml

@@ -9,8 +9,7 @@ WORKFLOW INSTRUCTIONS:
 2. READ its entire contents
 3. FOLLOW every step precisely as specified
 4. DO NOT skip or modify any steps
-
+5. RULE: When interaction_style is "structured", EVERY question to the user MUST call the ask_user tool. Do NOT write questions as plain text. No exceptions.
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the ask_user tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
 
 WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{workflow_path}}
 """

tools/cli/installers/lib/ide/templates/combined/kiro-agent.md

@@ -6,7 +6,7 @@ inclusion: manual
 
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. Do NOT ask open-ended inline questions. No exceptions.
 
 <agent-activation CRITICAL="TRUE">
 1. LOAD the FULL agent file from #[[file:{{bmadFolderName}}/{{path}}]]

tools/cli/installers/lib/ide/templates/combined/kiro-task.md

@@ -8,4 +8,4 @@ Read the entire task file at: #[[file:{{bmadFolderName}}/{{path}}]]
 
 Follow all instructions in the task file exactly as written.
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.

tools/cli/installers/lib/ide/templates/combined/kiro-tool.md

@@ -8,4 +8,4 @@ Read the entire tool file at: #[[file:{{bmadFolderName}}/{{path}}]]
 
 Follow all instructions in the tool file exactly as written.
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.

tools/cli/installers/lib/ide/templates/combined/kiro-workflow-yaml.md

@@ -4,7 +4,7 @@ inclusion: manual
 
 # {{name}}
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. Do NOT ask open-ended inline questions. No exceptions.
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 

tools/cli/installers/lib/ide/templates/combined/kiro-workflow.md

@@ -4,6 +4,6 @@ inclusion: manual
 
 # {{name}}
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. Do NOT ask open-ended inline questions. No exceptions.
 
 IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL #[[file:{{bmadFolderName}}/{{path}}]], READ its entire contents and follow its directions exactly!

tools/cli/installers/lib/ide/templates/combined/opencode-agent.md

@@ -5,7 +5,7 @@ description: '{{description}}'
 
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `question` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
 
 <agent-activation CRITICAL="TRUE">
 1. LOAD the FULL agent file from {project-root}/{{bmadFolderName}}/{{path}}

tools/cli/installers/lib/ide/templates/combined/opencode-task.md

@@ -10,6 +10,6 @@ TASK INSTRUCTIONS:
 2. READ its entire contents
 3. FOLLOW every instruction precisely as specified
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `question` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
 
 TASK FILE: {project-root}/{{bmadFolderName}}/{{path}}

tools/cli/installers/lib/ide/templates/combined/opencode-tool.md

@@ -10,6 +10,6 @@ TOOL INSTRUCTIONS:
 2. READ its entire contents
 3. FOLLOW every instruction precisely as specified
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `question` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
 
 TOOL FILE: {project-root}/{{bmadFolderName}}/{{path}}

tools/cli/installers/lib/ide/templates/combined/opencode-workflow-yaml.md

@@ -12,7 +12,6 @@ WORKFLOW INSTRUCTIONS:
 2. READ its entire contents
 3. FOLLOW every step precisely as specified
 4. DO NOT skip or modify any steps
-
+5. RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `question` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
 
 WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{path}}

tools/cli/installers/lib/ide/templates/combined/opencode-workflow.md

@@ -12,7 +12,6 @@ WORKFLOW INSTRUCTIONS:
 2. READ its entire contents
 3. FOLLOW every step precisely as specified
 4. DO NOT skip or modify any steps
-
+5. RULE: When interaction_style is "structured", EVERY question to the user MUST call the question tool. Do NOT write questions as plain text. No exceptions.
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST call the `question` tool unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
 
 WORKFLOW FILE: {project-root}/{{bmadFolderName}}/{{path}}

tools/cli/installers/lib/ide/templates/combined/rovodev.md

@@ -4,8 +4,8 @@
 
 ---
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+Read the entire workflow file at: {project-root}/_bmad/{{workflow_path}}
-
-Read the entire workflow file at: {project-root}/{{bmadFolderName}}/{{workflow_path}}
 
 Follow all instructions in the workflow file exactly as written.
+
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.

tools/cli/installers/lib/ide/templates/combined/trae.md

@@ -4,8 +4,8 @@
 
 ## Instructions
 
-Read the entire workflow file at: {project-root}/{{bmadFolderName}}/{{workflow_path}}
+Read the entire workflow file at: {project-root}/_bmad/{{workflow_path}}
 
 Follow all instructions in the workflow file exactly as written.
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.

tools/cli/installers/lib/ide/templates/combined/windsurf-workflow.md

@@ -5,8 +5,8 @@ auto_execution_mode: "iterate"
 
 # {{name}}
 
-Read the entire workflow file at {project-root}/{{bmadFolderName}}/{{workflow_path}}
+Read the entire workflow file at {project-root}/_bmad/{{workflow_path}}
 
 Follow all instructions in the workflow file exactly as written.
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. No exceptions.

tools/cli/installers/lib/ide/templates/workflow-command-template.md

@@ -2,7 +2,7 @@
 description: '{{description}}'
 ---
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. Do NOT ask open-ended inline questions. No exceptions.
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 

tools/cli/installers/lib/ide/templates/workflow-commander.md

@@ -2,6 +2,6 @@
 description: '{{description}}'
 ---
 
-RULE: Check your stored {interaction_style} session variable from activation step 2. When its value is "structured", EVERY question to the user MUST use structured options with a numbered list unless the workflow or user explicitly requests free-form input. If you cannot determine {interaction_style}, default to open mode.
+RULE: When interaction_style is "structured", EVERY question to the user MUST use structured options with a numbered list. Do NOT ask open-ended inline questions. No exceptions.
 
 IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{{workflow_path}}, READ its entire contents and follow its directions exactly!