bmad-method 6.0.0-alpha.8 → 6.0.0-alpha.9

package/src/core/tasks/workflow.xml

@@ -62,17 +62,33 @@
           <tag>ask xml tag → Prompt user and WAIT for response</tag>
           <tag>invoke-workflow xml tag → Execute another workflow with given inputs</tag>
           <tag>invoke-task xml tag → Execute specified task</tag>
+          <tag>invoke-protocol name="protocol_name" xml tag → Execute reusable protocol from protocols section</tag>
           <tag>goto step="x" → Jump to specified step</tag>
         </execute-tags>
       </substep>
 
-      <substep n="2c" title="Handle Special Output Tags">
+      <substep n="2c" title="Handle template-output Tags">
         <if tag="template-output">
           <mandate>Generate content for this section</mandate>
           <mandate>Save to file (Write first time, Edit subsequent)</mandate>
           <action>Show checkpoint separator: ━━━━━━━━━━━━━━━━━━━━━━━</action>
           <action>Display generated content</action>
-          <ask>Continue [c] or Edit [e]? WAIT for response</ask>
+          <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
+              response="a">
+              <action>Start the advanced elicitation workflow {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</action>
+            </if>
+            <if
+              response="c">
+              <action>Continue to next step</action>
+            </if>
+            <if response="p">
+              <action>Start the party-mode workflow {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml</action>
+            </if>
+            <if
+              response="y">
+              <action>Enter #yolo mode for the rest of the workflow</action>
+            </if>
+          </ask>
         </if>
       </substep>
 
@@ -92,7 +108,8 @@
 
   <execution-modes>
     <mode name="normal">Full user interaction at all decision points</mode>
-    <mode name="#yolo">Skip optional sections, skip all elicitation, minimize prompts</mode>
+    <mode name="#yolo">Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by
+      simulating the remaining discussions with an simulated expert user</mode>
   </execution-modes>
 
   <supported-tags desc="Instructions can use these tags">
@@ -111,6 +128,7 @@
       <tag>goto - Jump to another step</tag>
       <tag>invoke-workflow - Call another workflow</tag>
       <tag>invoke-task - Call a task</tag>
+      <tag>invoke-protocol - Execute a reusable protocol (e.g., discover_inputs)</tag>
     </execution>
     <output>
       <tag>template-output - Save content checkpoint</tag>
@@ -130,24 +148,120 @@
     <pattern type="multi-action-block">
       <use-case>Multiple actions/tags under same condition</use-case>
       <syntax>&lt;check if="condition"&gt;
-  &lt;action&gt;First action&lt;/action&gt;
-  &lt;action&gt;Second action&lt;/action&gt;
-&lt;/check&gt;</syntax>
+        &lt;action&gt;First action&lt;/action&gt;
+        &lt;action&gt;Second action&lt;/action&gt;
+        &lt;/check&gt;</syntax>
       <example>&lt;check if="validation fails"&gt;
-  &lt;action&gt;Log error&lt;/action&gt;
-  &lt;goto step="1"&gt;Retry&lt;/goto&gt;
-&lt;/check&gt;</example>
+        &lt;action&gt;Log error&lt;/action&gt;
+        &lt;goto step="1"&gt;Retry&lt;/goto&gt;
+        &lt;/check&gt;</example>
       <rationale>Explicit scope boundaries prevent ambiguity</rationale>
     </pattern>
 
     <pattern type="nested-conditions">
       <use-case>Else/alternative branches</use-case>
       <syntax>&lt;check if="condition A"&gt;...&lt;/check&gt;
-&lt;check if="else"&gt;...&lt;/check&gt;</syntax>
+        &lt;check if="else"&gt;...&lt;/check&gt;</syntax>
       <rationale>Clear branching logic with explicit blocks</rationale>
     </pattern>
   </conditional-execution-patterns>
 
+  <protocols desc="Reusable workflow protocols that can be invoked via invoke-protocol tag">
+    <protocol name="discover_inputs" desc="Smart file discovery and loading based on input_file_patterns">
+      <objective>Intelligently load project files (whole or sharded) based on workflow's input_file_patterns configuration</objective>
+
+      <critical>Only execute if workflow.yaml contains input_file_patterns section</critical>
+
+      <flow>
+        <step n="1" title="Parse Input File Patterns">
+          <action>Read input_file_patterns from loaded workflow.yaml</action>
+          <action>For each pattern group (prd, architecture, epics, etc.), note the load_strategy if present</action>
+        </step>
+
+        <step n="2" title="Load Files Using Smart Strategies">
+          <iterate>For each pattern in input_file_patterns:</iterate>
+
+          <substep n="2a" title="Try Whole Document First">
+            <action>Attempt glob match on 'whole' pattern (e.g., "{output_folder}/*prd*.md")</action>
+            <check if="matches found">
+              <action>Load ALL matching files completely (no offset/limit)</action>
+              <action>Store content in variable: {pattern_name_content} (e.g., {prd_content})</action>
+              <action>Mark pattern as RESOLVED, skip to next pattern</action>
+            </check>
+          </substep>
+
+          <substep n="2b" title="Try Sharded Document if Whole Not Found">
+            <check if="no whole matches AND sharded pattern exists">
+              <action>Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified)</action>
+
+              <strategy name="FULL_LOAD">
+                <desc>Load ALL files in sharded directory - used for PRD, Architecture, UX, brownfield docs</desc>
+                <action>Use glob pattern to find ALL .md files (e.g., "{output_folder}/*architecture*/*.md")</action>
+                <action>Load EVERY matching file completely</action>
+                <action>Concatenate content in logical order (index.md first if exists, then alphabetical)</action>
+                <action>Store in variable: {pattern_name_content}</action>
+              </strategy>
+
+              <strategy name="SELECTIVE_LOAD">
+                <desc>Load specific shard using template variable - example: used for epics with {{epic_num}}</desc>
+                <action>Check for template variables in sharded_single pattern (e.g., {{epic_num}})</action>
+                <action>If variable undefined, ask user for value OR infer from context</action>
+                <action>Resolve template to specific file path</action>
+                <action>Load that specific file</action>
+                <action>Store in variable: {pattern_name_content}</action>
+              </strategy>
+
+              <strategy name="INDEX_GUIDED">
+                <desc>Load index.md, analyze structure and description of each doc in the index, then intelligently load relevant docs</desc>
+                <mandate>DO NOT BE LAZY - use best judgment to load documents that might have relevant information, even if only a 5% chance</mandate>
+                <action>Load index.md from sharded directory</action>
+                <action>Parse table of contents, links, section headers</action>
+                <action>Analyze workflow's purpose and objective</action>
+                <action>Identify which linked/referenced documents are likely relevant</action>
+                <example>If workflow is about authentication and index shows "Auth Overview", "Payment Setup", "Deployment" → Load auth
+                  docs, consider deployment docs, skip payment</example>
+                <action>Load all identified relevant documents</action>
+                <action>Store combined content in variable: {pattern_name_content}</action>
+                <note>When in doubt, LOAD IT - context is valuable, being thorough is better than missing critical info</note>
+              </strategy>
+            </check>
+          </substep>
+
+          <substep n="2c" title="Handle Not Found">
+            <check if="no matches for whole OR sharded">
+              <action>Set {pattern_name_content} to empty string</action>
+              <action>Note in session: "No {pattern_name} files found" (not an error, just unavailable, offer use change to provide)</action>
+            </check>
+          </substep>
+        </step>
+
+        <step n="3" title="Report Discovery Results">
+          <action>List all loaded content variables with file counts</action>
+          <example>
+            ✓ Loaded {prd_content} from 1 file: PRD.md
+            ✓ Loaded {architecture_content} from 5 sharded files: architecture/index.md, architecture/system-design.md, ...
+            ✓ Loaded {epics_content} from selective load: epics/epic-3.md
+            ○ No ux_design files found
+          </example>
+          <note>This gives workflow transparency into what context is available</note>
+        </step>
+      </flow>
+
+      <usage-in-instructions>
+        <example desc="Typical usage in workflow instructions.md">
+          &lt;step n="0" goal="Discover and load project context"&gt;
+          &lt;invoke-protocol name="discover_inputs" /&gt;
+          &lt;/step&gt;
+
+          &lt;step n="1" goal="Analyze requirements"&gt;
+          &lt;action&gt;Review {prd_content} for functional requirements&lt;/action&gt;
+          &lt;action&gt;Cross-reference with {architecture_content} for technical constraints&lt;/action&gt;
+          &lt;/step&gt;
+        </example>
+      </usage-in-instructions>
+    </protocol>
+  </protocols>
+
   <llm final="true">
     <mandate>This is the complete workflow execution engine</mandate>
     <mandate>You MUST Follow instructions exactly as written and maintain conversation context between steps</mandate>

package/src/core/tools/shard-doc.xml

@@ -57,6 +57,50 @@
       <i>- Any tool output or warnings</i>
       <action>Inform user that sharding completed successfully</action>
     </step>
+
+    <step n="6" title="Handle Original Document">
+      <critical>Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion</critical>
+      <action>Present user with options for the original document:</action>
+
+      <ask>What would you like to do with the original document `[source-document-name]`?
+
+Options:
+[d] Delete - Remove the original (recommended - shards can always be recombined)
+[m] Move to archive - Move original to a backup/archive location
+[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
+
+Your choice (d/m/k):</ask>
+
+      <check if="user selects 'd' (delete)">
+        <action>Delete the original source document file</action>
+        <action>Confirm deletion to user: "✓ Original document deleted: [source-document-path]"</action>
+        <note>The document can be reconstructed from shards by concatenating all section files in order</note>
+      </check>
+
+      <check if="user selects 'm' (move)">
+        <action>Determine default archive location: same directory as source, in an "archive" subfolder</action>
+        <action>Example: /path/to/architecture.md → /path/to/archive/architecture.md</action>
+        <ask>Archive location ([y] to use default: [default-archive-path], or provide custom path):</ask>
+        <action if="user accepts default">Use default archive path</action>
+        <action if="user provides custom path">Use custom archive path</action>
+        <action>Create archive directory if it doesn't exist</action>
+        <action>Move original document to archive location</action>
+        <action>Confirm move to user: "✓ Original document moved to: [archive-path]"</action>
+      </check>
+
+      <check if="user selects 'k' (keep)">
+        <action>Display warning to user:</action>
+        <output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
+
+This creates confusion because:
+- The discover_inputs protocol may load the wrong version
+- Updates to one won't reflect in the other
+- You'll have duplicate content taking up space
+
+Consider deleting or archiving the original document.</output>
+        <action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
+      </check>
+    </step>
   </flow>
 
   <halt-conditions critical="true">

package/src/core/workflows/brainstorming/README.md

@@ -20,26 +20,16 @@ The brainstorming workflow facilitates interactive brainstorming sessions using
 
 ## Usage
 
-### Basic Invocation
-
-```bash
-workflow brainstorming
-```
-
-### With Context Document
-
-```bash
-# Provide domain-specific context to guide the session
-workflow brainstorming --data /path/to/context.md
-```
-
 ### Configuration
 
-The workflow leverages configuration from `{bmad_folder}/cis/config.yaml`:
+The workflow leverages configuration from `{bmad_folder}/core/config.yaml`:
 
 - **output_folder**: Where session results are saved
 - **user_name**: Session participant identification
-- **brain_techniques**: CSV database of 36 creative techniques
+
+And the following has a default or can be passed in as an override for custom brainstorming scenarios.
+
+- **brain_techniques**: CSV database of 36 creative techniques, default is `./brain-methods.csv`
 
 ## Workflow Structure
 

package/src/core/workflows/brainstorming/instructions.md

@@ -158,6 +158,7 @@ Which approach would you prefer? (Enter 1-4)
 
   </step>
 
+<critical>Create the output document using the template, and record at the {{session_start_plan}} documenting the chosen techniques, along with which approach was used. For all remaining steps, progressively add to the document throughout the brainstorming</critical>
 </step>
 
 <step n="3" goal="Execute Techniques Interactively">
@@ -202,7 +203,7 @@ Example facilitation flow for any technique:
 
 4. Next Prompt: Pull next facilitation_prompt when ready to advance
 
-5. Monitor Energy: After 10-15 minutes, check if they want to continue or switch
+5. Monitor Energy: After a few rounds, check if they want to continue or switch
 
 The CSV provides the prompts - your role is to facilitate naturally in your unique voice.
 </example>
@@ -215,7 +216,7 @@ Continue engaging with the technique until the user indicates they want to:
 - End the session
 
 <energy-checkpoint>
-  After 15-20 minutes with a technique, check: "Should we continue with this technique or try something new?"
+  After 4 rounds with a technique, check: "Should we continue with this technique or try something new?"
 </energy-checkpoint>
 
 <template-output>technique_sessions</template-output>
@@ -254,7 +255,7 @@ Analyze the session to identify deeper patterns:
 2. **Surface key insights** - What realizations emerged during the process? -> insights_learnings
 3. **Note surprising connections** - What unexpected relationships were discovered? -> insights_learnings
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
+<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>
 
 <template-output>key_themes, insights_learnings</template-output>
 

package/src/core/workflows/brainstorming/template.md

@@ -4,6 +4,10 @@
 **Facilitator:** {{agent_role}} {{agent_name}}
 **Participant:** {{user_name}}
 
+## Session Start
+
+{{session_start_plan}}
+
 ## Executive Summary
 
 **Topic:** {{session_topic}}

package/src/modules/bmb/workflows/audit-workflow/checklist.md

@@ -125,10 +125,9 @@ _List any cleanup recommendations:_
 
 ## Audit Summary
 
-**Total Checks:** 72
-**Passed:** **\_** / 72
-**Failed:** **\_** / 72
-**Pass Rate:** **\_**%
+**Total Checks:**
+**Passed:** {total}
+**Failed:** {total}
 
 **Recommendation:**
 

package/src/modules/bmb/workflows/convert-legacy/README.md

@@ -126,7 +126,7 @@ convert-legacy/
 **Template-to-Workflow Conversion (5c)**
 
 - Converts YAML template sections to workflow steps
-- Maps `elicit: true` flags to `<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>` tags
+- Maps `elicit: true` flags to `<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>` tags
 - Transforms conditional sections to flow control
 - Creates proper template.md from content structure
 - Integrates v4 create-doc.md task patterns

package/src/modules/bmb/workflows/convert-legacy/checklist.md

@@ -48,7 +48,7 @@
 - [ ] All sections converted to workflow steps
 - [ ] Section hierarchy maintained in instructions
 - [ ] Variables ({{var}}) preserved in template.md
-- [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
+- [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>
 - [ ] Conditional sections preserved with if="" attributes
 - [ ] Repeatable sections converted to repeat="" attributes
 

package/src/modules/bmb/workflows/convert-legacy/instructions.md

@@ -193,7 +193,7 @@ For Modules:
 
 2. Convert template sections to instructions.md:
    - Each YAML section → workflow step
-   - `elicit: true` → `<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>` tag
+   - `elicit: true` → `<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>` tag
    - Conditional sections → `if="condition"` attribute
    - Repeatable sections → `repeat="for-each"` attribute
    - Section instructions → step content
@@ -277,7 +277,7 @@ date: system-generated
    </check>
 
 4. Handle special v4 patterns:
-   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
+   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>
    - Agent permissions → note in instructions
    - YOLO mode → autonomous flag or optional steps
    - Critical notices → workflow.yaml comments

package/src/modules/bmb/workflows/create-agent/agent-architecture.md

@@ -7,10 +7,6 @@ _LLM-Optimized Technical Documentation for Agent Building_
 ### Minimal Valid Agent
 
 ```xml
-<!-- Powered by BMAD-CORE™ -->
-
-# Agent Name
-
 <agent id="path/to/agent.md" name="Name" title="Title" icon="🤖">
   <persona>
     <role>My primary function</role>

package/src/modules/bmb/workflows/create-agent/instructions.md

@@ -186,8 +186,7 @@ Note any interaction preferences for future workflow creation.
 - New workflows needed: Note that they'll be created with intent-based + interactive defaults unless specified
   </action>
 
-<example>
-```yaml
+<example type='yaml'>
 menu:
   # Commands emerge from discussion
   - trigger: [emerging from conversation]
@@ -200,9 +199,7 @@ menu:
   workflow: "{project-root}/{bmad_folder}/SOURCE_MODULE/workflows/path/to/workflow.yaml"
   workflow-install: "{project-root}/{bmad_folder}/THIS_MODULE/workflows/vendored/path/workflow.yaml"
   description: [description]
-
-`````
-</example>
+  </example>
 
 <note>**Workflow Vendoring (Advanced):**
 When an agent needs workflows from another module, use both `workflow` (source) and `workflow-install` (destination).
@@ -244,14 +241,14 @@ This is typically used when creating specialized modules that reuse common workf
       icon: {{agent_icon}} # The perfect emoji
       module: {{target_module}}
 
-persona:
-role: |
-{{The role discovered}}
-identity: |
-{{The background that emerged}}
-communication_style: |
-{{The style they loved}}
-principles: {{The beliefs articulated}}
+    persona:
+      role: |
+      {{The role discovered}}
+      identity: |
+      {{The background that emerged}}
+      communication_style: |
+      {{The style they loved}}
+      principles: {{The beliefs articulated}}
 
 # Features explored
 
@@ -312,7 +309,7 @@ menu: {{The capabilities built}}
 
 **Folder Structure:**
 
-`````
+```text
 
 {{agent_filename}}-sidecar/
 ├── memories.md # Persistent memory
@@ -321,7 +318,7 @@ menu: {{The capabilities built}}
 │ └── README.md
 └── sessions/ # Session notes
 
-````
+```
 
 **File: memories.md**
 
@@ -339,7 +336,7 @@ menu: {{The capabilities built}}
 ## Personal Notes
 
 <!-- My observations and insights -->
-````
+```
 
 **File: instructions.md**
 

package/src/modules/bmb/workflows/create-module/checklist.md

@@ -233,12 +233,3 @@
 - [ ] Alpha (Core functionality works)
 - [ ] Beta (Most features complete, needs testing)
 - [ ] Release (Full functionality, documented)
-
-## Sign-off
-
-**Module Name:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Module Code:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Version:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Validated By:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Date:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
-**Status:** ⬜ Pass / ⬜ Pass with Issues / ⬜ Fail

package/src/modules/bmb/workflows/create-module/instructions.md

@@ -180,7 +180,7 @@
 └── data/                     # User data directory
 ```
 
-**SOURCE MODULE** (\_module-installer is for installation only, not copied to target):
+**SOURCE MODULE** (module-installer is for installation only, not copied to target):
 
 ```
 {{module_code}}/
@@ -268,7 +268,7 @@
 <critical>IMPORTANT: Create install-config.yaml NOT install-config.yaml</critical>
 <critical>This is the STANDARD format that BMAD installer uses</critical>
 
-Create \_module-installer/install-config.yaml:
+Create module-installer/install-config.yaml:
 
 ```yaml
 # {{module_name}} Module Configuration
@@ -329,7 +329,7 @@ prompt:
 
 <critical>Save location:</critical>
 
-- Save to {{module_path}}/\_module-installer/install-config.yaml
+- Save to {{module_path}}/module-installer/install-config.yaml
 
 <ask>Does your module need custom installation logic (database setup, API registration, etc.)?</ask>
 
@@ -338,18 +338,13 @@ prompt:
   // {{module_name}} Module Installer
   // Custom installation logic
 
-/\*\*
-
-- Module installation hook
-- Called after files are copied but before IDE configuration
--
 - @param {Object} options - Installation options
 - @param {string} options.projectRoot - Project root directory
 - @param {Object} options.config - Module configuration from install-config.yaml
 - @param {Array} options.installedIDEs - List of IDE codes being configured
 - @param {Object} options.logger - Logger instance (log, warn, error methods)
 - @returns {boolean} - true if successful, false to abort installation
-  \*/
+
   async function install(options) {
   const { projectRoot, config, installedIDEs, logger } = options;
 
@@ -374,7 +369,7 @@ module.exports = { install };
 
 <critical>Save location:</critical>
 
-- Save to {{module_path}}/\_module-installer/installer.js
+- Save to {{module_path}}/module-installer/installer.js
 </check>
 
 <check if="no">

package/src/modules/bmb/workflows/create-module/module-structure.md

@@ -172,7 +172,7 @@ menu:
 
 ## Installation Infrastructure
 
-### Required: \_module-installer/install-config.yaml
+### Required: module-installer/install-config.yaml
 
 This file defines both installation questions AND static configuration values:
 
@@ -226,7 +226,7 @@ data_path:
 - `result` field uses placeholders: `{value}`, `{project-root}`, `{directory_name}`
 - Installer generates final `config.yaml` from this template
 
-### Optional: \_module-installer/installer.js
+### Optional: module-installer/installer.js
 
 For complex installations requiring custom logic:
 
@@ -252,7 +252,7 @@ async function install(options) {
 module.exports = { install };
 ```
 
-### Optional: \_module-installer/assets/
+### Optional: module-installer/assets/
 
 Files to copy during installation:
 

package/src/modules/bmb/workflows/create-workflow/instructions.md

@@ -328,7 +328,7 @@ Generate the instructions.md file following the workflow creation guide:
 
 4. Use proper XML tags from guide:
    - Execution: <action>, <check>, <ask>, <goto>, <invoke-workflow>
-   - Output: <template-output>, <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>, <critical>, <example>
+   - Output: <template-output>, <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>, <critical>, <example>
    - Flow: <loop>, <break>, <continue>
 
 5. Best practices from guide:

package/src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md

@@ -855,7 +855,6 @@ _Generated on {{date}}_
 **Output:**
 
 - `<template-output>` - Save checkpoint
-- `<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>` - Trigger AI enhancement
 - `<critical>` - Important info
 - `<example>` - Show example
 
@@ -904,7 +903,6 @@ _Generated on {{date}}_
   <step n="2" goal="Define requirements">
     Create functional and non-functional requirements.
     <template-output>requirements</template-output>
-    <invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
   </step>
 
   <step n="3" goal="Validate">

package/src/modules/bmb/workflows/module-brief/checklist.md

@@ -112,5 +112,5 @@
 
 **Validation Complete:** ⬜ Yes / ⬜ With Issues / ⬜ Needs Revision
 
-**Validated By:** **\*\*\*\***\_**\*\*\*\***
-**Date:** **\*\*\*\***\_**\*\*\*\***
+**Validated By:** {name}
+**Date:** {date}

package/src/modules/bmgd/_module-installer/install-config.yaml

@@ -21,19 +21,9 @@ game_project_name:
   default: "{directory_name}"
   result: "{value}"
 
-game_design_docs:
-  prompt: "Where should game design and planning documents (GDD, narrative, etc.) be stored?"
-  default: "{output_folder}/design"
-  result: "{project-root}/{value}"
-
-tech_docs:
-  prompt: "Where should technical reference documents be stored?"
-  default: "{output_folder}/technical"
-  result: "{project-root}/{value}"
-
-dev_ephemeral_location:
-  prompt: "Where should ephemeral development artifacts be stored (stories, epics, temp context, etc...)?"
-  default: "{bmad_folder}-ephemeral"
+sprint_artifacts:
+  prompt: "Where should Sprint Artifacts be stored (stories, epics, temp context, etc...)?"
+  default: "{output_folder}/sprint-artifacts"
   result: "{project-root}/{value}"
 
 game_dev_experience:
@@ -48,7 +38,7 @@ game_dev_experience:
     - value: "expert"
       label: "Expert - Experienced game developer, be direct and technical"
 
-specified_framework:
+primary_platform:
   prompt: "Which game development framework or engine do you want to install support for?"
   default: ["unity", "unreal", "godot", "other"]
   required: true
@@ -62,6 +52,3 @@ specified_framework:
       label: "Godot"
     - value: "other"
       label: "Custom / Other"
-
-data_path:
-  result: "{project-root}/{bmad_folder}/bmgd/data"

package/src/modules/bmgd/agents/game-architect.agent.yaml

@@ -28,6 +28,6 @@ agent:
       workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
       description: Consult with other expert agents from the party
 
-    - trigger: adv-elicit
-      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
+    - trigger: advanced-elicitation
+      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results

package/src/modules/bmgd/agents/game-designer.agent.yaml

@@ -35,6 +35,6 @@ agent:
       workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
       description: Consult with other expert agents from the party
 
-    - trigger: adv-elicit
-      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
+    - trigger: advanced-elicitation
+      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results

package/src/modules/bmgd/agents/game-dev.agent.yaml

@@ -35,6 +35,6 @@ agent:
       workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
       description: Consult with other expert agents from the party
 
-    - trigger: adv-elicit
-      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
+    - trigger: advanced-elicitation
+      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results