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

package/.bmad/bmm/workflows/workflow-status/paths/game-design.yaml

@@ -0,0 +1,52 @@
+# Game Development - Use BMGD Module
+# Game development workflows have been moved to the BMad Game Development module
+
+project_type: "game"
+level: "all"
+field_type: "any"
+description: "⚠️ Game development requires the BMGD module"
+
+error_message: |
+  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+  🎮 **GAME DEVELOPMENT DETECTED**
+
+  Game development workflows are now part of the **BMad Game Development (BMGD)** module,
+  which provides specialized workflows and agents for game creation.
+
+  **To proceed with game development:**
+
+  1. Install the BMGD module:
+     ```bash
+     bmad install bmgd
+     ```
+
+  2. The BMGD module includes:
+     - Game Designer, Game Developer, Game Architect agents
+     - Game Dev Scrum Master for sprint coordination
+     - Industry-standard game dev workflows:
+       • Phase 1 (Preproduction): brainstorm-game, game-brief
+       • Phase 2 (Design): GDD, narrative design
+       • Phase 3 (Technical): game architecture
+       • Phase 4 (Production): sprint planning, story management
+
+  3. After installation, load the Game Designer or Game Dev Scrum Master agent
+     to begin your game development workflow
+
+  **Why a separate module?**
+  - Game development follows different phases than software development
+  - Specialized agents understand game-specific terminology and patterns
+  - Workflows configured for game development needs (playtesting, balancing, etc.)
+  - Can be used standalone or alongside BMM for complete coverage
+
+  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+# Placeholder phases - this file should not be used for actual workflow tracking
+# Users should install BMGD module instead
+phases:
+  - phase: 1
+    name: "ERROR - Install BMGD Module"
+    workflows:
+      - id: "install-bmgd"
+        required: true
+        note: "Run: bmad install bmgd"

package/.bmad/bmm/workflows/workflow-status/paths/method-brownfield.yaml

@@ -0,0 +1,97 @@
+# BMad Method - Brownfield
+# Full product + architecture planning for complex brownfield additions (10-50+ stories typically)
+
+method_name: "BMad Method"
+track: "method"
+field_type: "brownfield"
+description: "Complete product and system design for complex brownfield work"
+
+phases:
+  - prerequisite: true
+    name: "Documentation"
+    conditional: "if_undocumented"
+    note: "NOT a phase - prerequisite for brownfield without docs"
+    workflows:
+      - id: "document-project"
+        required: true
+        agent: "analyst"
+        command: "document-project"
+        output: "Comprehensive project documentation"
+        purpose: "Understand existing codebase before planning"
+
+  - phase: 0
+    name: "Discovery (Optional)"
+    optional: true
+    note: "User-selected during workflow-init"
+    workflows:
+      - id: "brainstorm-project"
+        optional: true
+        agent: "analyst"
+        command: "brainstorm-project"
+        included_by: "user_choice"
+
+      - id: "research"
+        optional: true
+        agent: "analyst"
+        command: "research"
+        included_by: "user_choice"
+
+      - id: "product-brief"
+        optional: true
+        agent: "analyst"
+        command: "product-brief"
+        included_by: "user_choice"
+        note: "Optional for brownfield, less common than greenfield"
+
+  - phase: 1
+    name: "Planning"
+    required: true
+    workflows:
+      - id: "prd"
+        required: true
+        agent: "pm"
+        command: "prd"
+        output: "PRD focused on new features/changes"
+        note: "Must consider existing system constraints"
+
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
+
+      - id: "create-design"
+        conditional: "if_has_ui"
+        agent: "ux-designer"
+        command: "create-design"
+
+  - phase: 2
+    name: "Solutioning"
+    required: true
+    workflows:
+      - id: "create-architecture"
+        recommended: true
+        agent: "architect"
+        command: "create-architecture"
+        output: "Integration architecture - solution design for THIS project"
+        note: "HIGHLY RECOMMENDED: Distills massive brownfield context into focused solution design. Prevents agent confusion."
+
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
+
+      - id: "solutioning-gate-check"
+        required: true
+        agent: "architect"
+        command: "solutioning-gate-check"
+        note: "Validates PRD + UX + Architecture (if created) cohesion"
+
+  - phase: 3
+    name: "Implementation"
+    required: true
+    workflows:
+      - id: "sprint-planning"
+        required: true
+        agent: "sm"
+        command: "sprint-planning"
+        note: "Creates sprint plan with stories"

package/.bmad/bmm/workflows/workflow-status/paths/method-greenfield.yaml

@@ -0,0 +1,88 @@
+# BMad Method - Greenfield
+# Full product + architecture planning for greenfield projects (10-50+ stories typically)
+
+method_name: "BMad Method"
+track: "method"
+field_type: "greenfield"
+description: "Complete product and system design methodology for greenfield projects"
+
+phases:
+  - phase: 0
+    name: "Discovery (Optional)"
+    optional: true
+    note: "User-selected during workflow-init"
+    workflows:
+      - id: "brainstorm-project"
+        optional: true
+        agent: "analyst"
+        command: "brainstorm-project"
+        included_by: "user_choice"
+
+      - id: "research"
+        optional: true
+        agent: "analyst"
+        command: "research"
+        included_by: "user_choice"
+        note: "Can have multiple research workflows"
+
+      - id: "product-brief"
+        optional: true
+        agent: "analyst"
+        command: "product-brief"
+        included_by: "user_choice"
+        note: "Recommended for greenfield Method projects"
+
+  - phase: 1
+    name: "Planning"
+    required: true
+    workflows:
+      - id: "prd"
+        required: true
+        agent: "pm"
+        command: "prd"
+        output: "Product Requirements Document with epics and stories"
+
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
+        note: "Quality check for PRD completeness"
+
+      - id: "create-design"
+        conditional: "if_has_ui"
+        agent: "ux-designer"
+        command: "create-design"
+        note: "Determined after PRD - user/agent decides if needed"
+
+  - phase: 2
+    name: "Solutioning"
+    required: true
+    workflows:
+      - id: "create-architecture"
+        required: true
+        agent: "architect"
+        command: "create-architecture"
+        output: "System architecture document"
+        note: "Complete system design for greenfield projects"
+
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
+        note: "Quality check for architecture completeness"
+
+      - id: "solutioning-gate-check"
+        required: true
+        agent: "architect"
+        command: "solutioning-gate-check"
+        note: "Validates PRD + UX + Architecture cohesion before implementation"
+
+  - phase: 3
+    name: "Implementation"
+    required: true
+    workflows:
+      - id: "sprint-planning"
+        required: true
+        agent: "sm"
+        command: "sprint-planning"
+        note: "Creates sprint plan - subsequent work tracked there"

package/.bmad/bmm/workflows/workflow-status/paths/quick-flow-brownfield.yaml

@@ -0,0 +1,58 @@
+# BMad Quick Flow - Brownfield
+# Fast implementation path for existing codebases (1-15 stories typically)
+
+method_name: "BMad Quick Flow"
+track: "quick-flow"
+field_type: "brownfield"
+description: "Fast tech-spec based implementation for brownfield projects"
+
+phases:
+  - prerequisite: true
+    name: "Documentation"
+    conditional: "if_undocumented"
+    note: "NOT a phase - prerequisite for brownfield without docs"
+    workflows:
+      - id: "document-project"
+        required: true
+        agent: "analyst"
+        command: "document-project"
+        output: "Comprehensive project documentation"
+        purpose: "Understand existing codebase before planning"
+
+  - phase: 0
+    name: "Discovery (Optional)"
+    optional: true
+    note: "User-selected during workflow-init"
+    workflows:
+      - id: "brainstorm-project"
+        optional: true
+        agent: "analyst"
+        command: "brainstorm-project"
+        included_by: "user_choice"
+
+      - id: "research"
+        optional: true
+        agent: "analyst"
+        command: "research"
+        included_by: "user_choice"
+
+  - phase: 1
+    name: "Planning"
+    required: true
+    workflows:
+      - id: "tech-spec"
+        required: true
+        agent: "pm"
+        command: "tech-spec"
+        output: "Technical Specification with stories (auto-detects epic if 2+ stories)"
+        note: "Integrates with existing codebase patterns from document-project"
+
+  - phase: 2
+    name: "Implementation"
+    required: true
+    workflows:
+      - id: "sprint-planning"
+        required: true
+        agent: "sm"
+        command: "sprint-planning"
+        note: "Creates sprint plan with all stories"

package/.bmad/bmm/workflows/workflow-status/paths/quick-flow-greenfield.yaml

@@ -0,0 +1,47 @@
+# BMad Quick Flow - Greenfield
+# Fast implementation path with tech-spec planning (1-15 stories typically)
+
+method_name: "BMad Quick Flow"
+track: "quick-flow"
+field_type: "greenfield"
+description: "Fast tech-spec based implementation for greenfield projects"
+
+phases:
+  - phase: 0
+    name: "Discovery (Optional)"
+    optional: true
+    note: "User-selected during workflow-init"
+    workflows:
+      - id: "brainstorm-project"
+        optional: true
+        agent: "analyst"
+        command: "brainstorm-project"
+        included_by: "user_choice"
+
+      - id: "research"
+        optional: true
+        agent: "analyst"
+        command: "research"
+        included_by: "user_choice"
+        note: "Can have multiple research workflows"
+
+  - phase: 1
+    name: "Planning"
+    required: true
+    workflows:
+      - id: "tech-spec"
+        required: true
+        agent: "pm"
+        command: "tech-spec"
+        output: "Technical Specification with stories (auto-detects epic if 2+ stories)"
+        note: "Quick Spec Flow - implementation-focused planning"
+
+  - phase: 2
+    name: "Implementation"
+    required: true
+    workflows:
+      - id: "sprint-planning"
+        required: true
+        agent: "sm"
+        command: "sprint-planning"
+        note: "Creates sprint plan with all stories - subsequent work tracked in sprint plan output, not workflow-status"

package/.bmad/bmm/workflows/workflow-status/project-levels.yaml

@@ -0,0 +1,59 @@
+# BMM Project Scale Levels - Source of Truth
+# Reference: /.bmad/bmm/README.md lines 77-85
+
+levels:
+  0:
+    name: "Level 0"
+    title: "Single Atomic Change"
+    stories: "1 story"
+    description: "Bug fix, tiny feature, one small change"
+    documentation: "Minimal - tech spec only"
+    architecture: false
+
+  1:
+    name: "Level 1"
+    title: "Small Feature"
+    stories: "1-10 stories"
+    description: "Small coherent feature, minimal documentation"
+    documentation: "Tech spec"
+    architecture: false
+
+  2:
+    name: "Level 2"
+    title: "Medium Project"
+    stories: "5-15 stories"
+    description: "Multiple features, focused PRD"
+    documentation: "PRD + optional tech spec"
+    architecture: false
+
+  3:
+    name: "Level 3"
+    title: "Complex System"
+    stories: "12-40 stories"
+    description: "Subsystems, integrations, full architecture"
+    documentation: "PRD + architecture + JIT tech specs"
+    architecture: true
+
+  4:
+    name: "Level 4"
+    title: "Enterprise Scale"
+    stories: "40+ stories"
+    description: "Multiple products, enterprise architecture"
+    documentation: "PRD + architecture + JIT tech specs"
+    architecture: true
+
+# Quick detection hints for workflow-init
+detection_hints:
+  keywords:
+    level_0: ["fix", "bug", "typo", "small change", "quick update", "patch"]
+    level_1: ["simple", "basic", "small feature", "add", "minor"]
+    level_2: ["dashboard", "several features", "admin panel", "medium"]
+    level_3: ["platform", "integration", "complex", "system", "architecture"]
+    level_4: ["enterprise", "multi-tenant", "multiple products", "ecosystem", "scale"]
+
+  story_counts:
+    level_0: [1, 1]
+    level_1: [1, 10]
+    level_2: [5, 15]
+    level_3: [12, 40]
+    level_4: [40, 999]

package/.bmad/bmm/workflows/workflow-status/sample-level-3-workflow.yaml

@@ -0,0 +1,49 @@
+# Workflow Status Template
+# This tracks progress through phases 1-3 of the BMM methodology
+# Phase 4 (Implementation) is tracked separately in sprint-status.yaml
+
+# generated: 2025-10-29
+# project: Enterprise Customer Portal
+# project_type: software
+# project_level: 3
+# field_type: greenfield
+# workflow_path: greenfield-level-3.yaml
+
+# STATUS DEFINITIONS:
+# ==================
+# Initial Status (before completion):
+#   - required: Must be completed to progress
+#   - optional: Can be completed but not required
+#   - recommended: Strongly suggested but not required
+#   - conditional: Required only if certain conditions met (e.g., if_has_ui)
+#
+# Completion Status:
+#   - {file-path}: File created/found (e.g., "docs/product-brief.md")
+#   - skipped: Optional/conditional workflow that was skipped
+
+generated: 2025-10-29
+project: Enterprise Customer Portal
+project_type: software
+project_level: 3
+field_type: greenfield
+workflow_path: greenfield-level-3.yaml
+
+workflow_status:
+  # Phase 1: Analysis
+  brainstorm-project: docs/brainstorm-session-2025-10-15.md
+  research: docs/research-api-patterns.md
+  product-brief: docs/product-brief.md
+
+  # Phase 2: Planning
+  prd: docs/prd.md
+  validate-prd: skipped
+  create-design: docs/ux-design.md
+
+  # Phase 3: Solutioning
+  create-architecture: required
+  validate-architecture: optional
+  solutioning-gate-check: recommended
+
+  # Phase 4: Implementation
+  sprint-planning: required
+  # Note: Subsequent implementation workflows tracked in sprint-status.yaml

package/.bmad/bmm/workflows/workflow-status/workflow-status-template.yaml

@@ -0,0 +1,31 @@
+# Workflow Status Template
+# This tracks progress through BMM methodology phases
+# Phase 3/4 (Implementation) is tracked separately in sprint-status.yaml
+
+# generated: {{generated}}
+# project: {{project_name}}
+# project_type: {{project_type}}
+# selected_track: {{selected_track}}
+# field_type: {{field_type}}
+# workflow_path: {{workflow_path_file}}
+
+# STATUS DEFINITIONS:
+# ==================
+# Initial Status (before completion):
+#   - required: Must be completed to progress
+#   - optional: Can be completed but not required
+#   - recommended: Strongly suggested but not required
+#   - conditional: Required only if certain conditions met (e.g., if_has_ui)
+#
+# Completion Status:
+#   - {file-path}: File created/found (e.g., "docs/product-brief.md")
+#   - skipped: Optional/conditional workflow that was skipped
+
+generated: "{{generated}}"
+project: "{{project_name}}"
+project_type: "{{project_type}}"
+selected_track: "{{selected_track}}"
+field_type: "{{field_type}}"
+workflow_path: "{{workflow_path_file}}"
+
+workflow_status: "{{workflow_items}}"

package/.bmad/bmm/workflows/workflow-status/workflow.yaml

@@ -0,0 +1,28 @@
+# Workflow Status - Master Router and Status Tracker
+name: workflow-status
+description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/.bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/.bmad/bmm/workflows/workflow-status"
+instructions: "{installed_path}/instructions.md"
+
+# Template for status file creation (used by workflow-init)
+template: "{installed_path}/workflow-status-template.yaml"
+
+# Path definitions for project types
+path_files: "{installed_path}/paths/"
+
+# Output configuration - reads existing status
+default_output_file: "{output_folder}/bmm-workflow-status.yaml"
+
+standalone: true

package/{bmad → .bmad}/core/agents/bmad-master.md

@@ -6,16 +6,16 @@ description: 'BMad Master Executor, Knowledge Custodian, and Workflow Orchestrat
 You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 
 ```xml
-<agent id="bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" icon="🧙">
+<agent id=".bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" icon="🧙">
 <activation critical="MANDATORY">
   <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/core/config.yaml NOW
+      - Load and read {project-root}/{bmad_folder}/core/config.yaml NOW
       - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
       - 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>
   <step n="3">Remember: user's name is {user_name}</step>
-  <step n="4">Load into memory {project-root}/bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</step>
+  <step n="4">Load into memory {project-root}/.bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</step>
   <step n="5">Remember the users name is {user_name}</step>
   <step n="6">ALWAYS communicate in {communication_language}</step>
   <step n="7">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
@@ -35,7 +35,7 @@ You must fully embody this agent's persona and follow all activation instruction
 
   <handler type="workflow">
     When menu item has: workflow="path/to/workflow.yaml"
-    1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
+    1. CRITICAL: Always LOAD {project-root}/{bmad_folder}/core/tasks/workflow.xml
     2. Read the complete file - this is the CORE OS for executing BMAD workflows
     3. Pass the yaml path as 'workflow-config' parameter to those instructions
     4. Execute workflow.xml instructions precisely following all steps
@@ -62,9 +62,9 @@ You must fully embody this agent's persona and follow all activation instruction
   </persona>
   <menu>
     <item cmd="*help">Show numbered menu</item>
-    <item cmd="*list-tasks" action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">List Available Tasks</item>
-    <item cmd="*list-workflows" action="list all workflows from {project-root}/bmad/_cfg/workflow-manifest.csv">List Workflows</item>
-    <item cmd="*party-mode" workflow="{project-root}/bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</item>
+    <item cmd="*list-tasks" action="list all tasks from {project-root}/.bmad/_cfg/task-manifest.csv">List Available Tasks</item>
+    <item cmd="*list-workflows" action="list all workflows from {project-root}/.bmad/_cfg/workflow-manifest.csv">List Workflows</item>
+    <item cmd="*party-mode" workflow="{project-root}/.bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</item>
     <item cmd="*exit">Exit with confirmation</item>
   </menu>
 </agent>

package/{bmad → .bmad}/core/agents/bmad-web-orchestrator.agent.xml

@@ -1,7 +1,8 @@
-<agent id="bmad/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
+<agent id="{bmad_folder}/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
   <activation critical="MANDATORY">
     <step n="1">Load this complete web bundle XML - you are the BMad Orchestrator, first agent in this bundle</step>
-    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="bmad/..." and ALL workflows/tasks as nodes findable by type
+    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="{bmad_folder}/..." and ALL workflows/tasks as nodes findable
+      by type
       and id</step>
     <step n="3">Greet user as BMad Orchestrator and display numbered list of ALL menu items from menu section below</step>
     <step n="4">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
@@ -15,7 +16,7 @@
         <handler type="workflow">
           When menu item has: workflow="workflow-id"
           1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
-          2. CRITICAL: Always LOAD bmad/core/tasks/workflow.xml if referenced
+          2. CRITICAL: Always LOAD {bmad_folder}/core/tasks/workflow.xml if referenced
           3. Execute the workflow content precisely following all steps
           4. Save outputs after completing EACH workflow step (never batch)
           5. If workflow id is "todo", inform user it hasn't been implemented yet
@@ -48,7 +49,7 @@
 
         <handler type="validate-workflow">
           When menu item has: validate-workflow="workflow-id"
-          1. MUST LOAD bmad/core/tasks/validate-workflow.xml
+          1. MUST LOAD {bmad_folder}/core/tasks/validate-workflow.xml
           2. Execute all validation instructions from that file
           3. Check workflow's validation property for schema
           4. Identify file to validate or ask user to specify
@@ -69,18 +70,6 @@
         5. On *exit: Confirm, then return to BMad Orchestrator persona
       </agent-transformation>
 
-      <party-mode critical="true">
-        When user selects *party-mode:
-        1. Enter group chat simulation mode
-        2. Load ALL agent personas from this bundle
-        3. Simulate each agent distinctly with their name and emoji
-        4. Create engaging multi-agent conversation
-        5. Each agent contributes based on their expertise
-        6. Format: "[emoji] Name: message"
-        7. Maintain distinct voices and perspectives for each agent
-        8. Continue until user types *exit-party
-      </party-mode>
-
       <list-agents critical="true">
         When user selects *list-agents:
         1. Scan all agent nodes in this bundle
@@ -116,7 +105,9 @@
     <item cmd="*help">Show numbered command list</item>
     <item cmd="*list-agents">List all available agents with their capabilities</item>
     <item cmd="*agents [agent-name]">Transform into a specific agent</item>
-    <item cmd="*party-mode">Enter group chat with all agents simultaneously</item>
+    <item cmd="*party-mode" workflow="bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml">Enter group chat with all agents
+      simultaneously</item>
+    <item cmd="*adv-elicit" task="bmad/core/tasks/adv-elict.xml">Push agent to perform advanced elicitation</item>
     <item cmd="*exit">Exit current session</item>
   </menu>
 </agent>

package/{bmad → .bmad}/core/config.yaml

@@ -1,9 +1,11 @@
 # CORE Module Configuration
 # Generated by BMAD installer
-# Version: 6.0.0-alpha.6
-# Date: 2025-11-07T04:40:13.952Z
+# Version: 6.0.0-alpha.7
+# Date: 2025-11-09T05:23:00.244Z
 
+bmad_folder: .bmad
 user_name: BMad
 communication_language: English
 document_output_language: English
 output_folder: "{project-root}/docs"
+install_user_docs: false

package/{bmad → .bmad}/core/tasks/adv-elicit.xml

@@ -1,4 +1,6 @@
-<task id="bmad/core/tasks/adv-elicit.xml" name="Advanced Elicitation">
+<task id="{bmad_folder}/core/tasks/adv-elicit.xml" name="Advanced Elicitation" standalone="true"
+  methods="{project-root}/{bmad_folder}/core/tasks/adv-elicit-methods.csv"
+  agent-party="{project-root}/{bmad_folder}/_cfg/agent-manifest.csv">
   <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>
@@ -9,7 +11,7 @@
 
   <integration description="When called from workflow">
     <desc>When called during template workflow processing:</desc>
-    <i>1. Receive the current section content that was just generated</i>
+    <i>1. Receive or review the current section content that was just generated or</i>
     <i>2. Apply elicitation methods iteratively to enhance that specific content</i>
     <i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
     <i>4. The enhanced content replaces the original section content in the output document</i>
@@ -17,7 +19,7 @@
 
   <flow>
     <step n="1" title="Method Registry Loading">
-      <action>Load and read {project-root}/core/tasks/adv-elicit-methods.csv</action>
+      <action>Load and read {{methods}} and {{agent-party}}</action>
 
       <csv-structure>
         <i>category: Method grouping (core, structural, risk, etc.)</i>

package/{bmad → .bmad}/core/tasks/index-docs.xml

@@ -1,4 +1,4 @@
-<task id="bmad/core/tasks/index-docs" name="Index Docs"
+<task id="{bmad_folder}/core/tasks/index-docs" name="Index Docs"
   description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>