bmad-method 6.0.0-alpha.21 → 6.0.0-alpha.23

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-10-production.md

@@ -6,13 +6,13 @@ description: 'Plan production scope including writing estimates, localization, a
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-10-production.md'
-nextStepFile: '{workflow_path}/steps/step-11-complete.md'
+thisStepFile: './step-10-production.md'
+nextStepFile: './step-11-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Plan the production scope for narrative content: writing scope estimates, locali
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-11-complete.md

@@ -6,7 +6,7 @@ description: 'Complete the narrative workflow with final summary, visualizations
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-11-complete.md'
+thisStepFile: './step-11-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 
@@ -30,6 +30,7 @@ Generate final visualizations (character relationships, timeline), capture refer
 - CRITICAL: Read the complete step file before taking any action
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/2-design/narrative/workflow.md

@@ -36,7 +36,7 @@ stepsCompleted: [1, 2, 3, ...] # Array of completed step numbers
 To begin, load and execute step-01-init.md:
 
 ```
-{workflow_path}/steps/step-01-init.md
+./step-01-init.md
 ```
 
 ## Critical Rules
@@ -46,6 +46,7 @@ To begin, load and execute step-01-init.md:
 - **NEVER** mention time estimates
 - **ALWAYS** present options and wait for user selection
 - **FOLLOW** the step sequence exactly - no skipping or optimizing
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## Agent Role
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-01-init.md

@@ -6,9 +6,9 @@ description: 'Initialize the architecture workflow, validate readiness, and disc
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
-nextStepFile: '{workflow_path}/steps/step-02-context.md'
+thisStepFile: './step-01-init.md'
+continueStepFile: './step-01b-continue.md'
+nextStepFile: './step-02-context.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 templateFile: '{workflow_path}/templates/architecture-template.md'
@@ -36,6 +36,7 @@ Validate workflow readiness, check for existing architecture work, discover inpu
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-01b-continue.md

@@ -6,19 +6,19 @@ description: 'Continue an existing architecture workflow from where it left off'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 
 # Step Files (for routing)
-step02: '{workflow_path}/steps/step-02-context.md'
-step03: '{workflow_path}/steps/step-03-starter.md'
-step04: '{workflow_path}/steps/step-04-decisions.md'
-step05: '{workflow_path}/steps/step-05-crosscutting.md'
-step06: '{workflow_path}/steps/step-06-structure.md'
-step07: '{workflow_path}/steps/step-07-patterns.md'
-step08: '{workflow_path}/steps/step-08-validation.md'
-step09: '{workflow_path}/steps/step-09-complete.md'
+step02: './step-02-context.md'
+step03: './step-03-starter.md'
+step04: './step-04-decisions.md'
+step05: './step-05-crosscutting.md'
+step06: './step-06-structure.md'
+step07: './step-07-patterns.md'
+step08: './step-08-validation.md'
+step09: './step-09-complete.md'
 ---
 
 # Step 1b: Continue Existing Architecture
@@ -37,6 +37,7 @@ Load the existing architecture document, determine progress, and route to the ap
 - CRITICAL: Read the complete step file before taking any action
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Step-Specific Rules:
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-02-context.md

@@ -6,13 +6,13 @@ description: 'Load and understand project context from GDD and supporting docume
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-02-context.md'
-nextStepFile: '{workflow_path}/steps/step-03-starter.md'
+thisStepFile: './step-02-context.md'
+nextStepFile: './step-03-starter.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Load and analyze the GDD and supporting documents to understand the game's techn
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-03-starter.md

@@ -6,13 +6,13 @@ description: 'Discover and evaluate game engine and starter template options'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-03-starter.md'
-nextStepFile: '{workflow_path}/steps/step-04-decisions.md'
+thisStepFile: './step-03-starter.md'
+nextStepFile: './step-04-decisions.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Discover and evaluate game engine options and starter templates based on project
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-04-decisions.md

@@ -6,8 +6,8 @@ description: 'Facilitate collaborative architectural decision making for game sy
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-04-decisions.md'
-nextStepFile: '{workflow_path}/steps/step-05-crosscutting.md'
+thisStepFile: './step-04-decisions.md'
+nextStepFile: './step-05-crosscutting.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 
@@ -16,7 +16,7 @@ decisionCatalog: '{workflow_path}/decision-catalog.yaml'
 architecturePatterns: '{workflow_path}/architecture-patterns.yaml'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -37,6 +37,7 @@ Facilitate collaborative decision-making for all remaining architectural choices
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-05-crosscutting.md

@@ -6,13 +6,13 @@ description: 'Address cross-cutting concerns that affect all game systems'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-05-crosscutting.md'
-nextStepFile: '{workflow_path}/steps/step-06-structure.md'
+thisStepFile: './step-05-crosscutting.md'
+nextStepFile: './step-06-structure.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Define patterns for concerns that affect EVERY system in the game: error handlin
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-06-structure.md

@@ -6,13 +6,13 @@ description: 'Define project structure, directory organization, and architectura
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-06-structure.md'
-nextStepFile: '{workflow_path}/steps/step-07-patterns.md'
+thisStepFile: './step-06-structure.md'
+nextStepFile: './step-07-patterns.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -33,6 +33,7 @@ Define the complete project structure including directory organization, file nam
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 
@@ -212,7 +213,7 @@ Based on the conversation, prepare the content:
 ### System Location Mapping
 
 | System | Location | Responsibility |
-|--------|----------|----------------|
+| ------ | -------- | -------------- |
 {{system_mapping_table}}
 
 ### Naming Conventions
@@ -222,7 +223,7 @@ Based on the conversation, prepare the content:
 
 #### Code Elements
 | Element | Convention | Example |
-|---------|------------|---------|
+| ------- | ---------- | ------- |
 {{code_naming_table}}
 
 #### Game Assets

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-07-patterns.md

@@ -6,8 +6,8 @@ description: 'Design implementation patterns and novel architectural patterns fo
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-07-patterns.md'
-nextStepFile: '{workflow_path}/steps/step-08-validation.md'
+thisStepFile: './step-07-patterns.md'
+nextStepFile: './step-08-validation.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 
@@ -15,7 +15,7 @@ outputFile: '{output_folder}/game-architecture.md'
 patternCategories: '{workflow_path}/pattern-categories.csv'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -36,6 +36,7 @@ Define implementation patterns that ensure multiple AI agents write compatible,
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-08-validation.md

@@ -6,14 +6,14 @@ description: 'Validate architectural coherence and completeness'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-08-validation.md'
-nextStepFile: '{workflow_path}/steps/step-09-complete.md'
+thisStepFile: './step-08-validation.md'
+nextStepFile: './step-09-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 checklistFile: '{workflow_path}/checklist.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 ---
 
@@ -34,6 +34,7 @@ Validate that the architecture is coherent, complete, and ready to guide AI agen
 - CRITICAL: When loading next step with 'C', ensure entire file is read
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 
@@ -96,12 +97,12 @@ Verifying every GDD requirement has architectural support:
 
 **Core Systems:**
 | System | Architecture Support | Status |
-|--------|---------------------|--------|
+| ------ | -------------------- | ------ |
 {{systems_coverage_table}}
 
 **Technical Requirements:**
 | Requirement | How Addressed | Status |
-|-------------|---------------|--------|
+| ----------- | ------------- | ------ |
 {{requirements_coverage_table}}
 
 {{if_gaps_found}}

package/src/modules/bmgd/workflows/3-technical/game-architecture/steps/step-09-complete.md

@@ -6,7 +6,7 @@ description: 'Complete the architecture workflow with final review and handoff g
 workflow_path: '{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-09-complete.md'
+thisStepFile: './step-09-complete.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/game-architecture.md'
 
@@ -31,6 +31,7 @@ Generate the executive summary, finalize the document, update workflow status, a
 - CRITICAL: Read the complete step file before taking any action
 - YOU ARE A FACILITATOR, not a content generator
 - NEVER mention time estimates
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/workflow.md

@@ -34,7 +34,7 @@ stepsCompleted: [1, 2, 3, ...] # Array of completed step numbers
 To begin, load and execute step-01-init.md:
 
 ```
-{workflow_path}/steps/step-01-init.md
+./step-01-init.md
 ```
 
 ## Critical Rules
@@ -44,6 +44,7 @@ To begin, load and execute step-01-init.md:
 - **NEVER** mention time estimates
 - **ALWAYS** present options and wait for user selection
 - **FOLLOW** the step sequence exactly - no skipping or optimizing
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## Agent Role
 

package/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-01-discover.md

@@ -8,6 +8,7 @@
 - FOCUS on discovering existing project context and technology stack
 - IDENTIFY critical implementation rules that AI agents need
 - ABSOLUTELY NO TIME ESTIMATES
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-02-generate.md

@@ -8,6 +8,7 @@
 - FOCUS on unobvious rules that AI agents need to be reminded of
 - KEEP CONTENT LEAN - optimize for LLM context efficiency
 - ABSOLUTELY NO TIME ESTIMATES
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -28,7 +29,7 @@ This step will generate content and present choices for each rule category:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

package/src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-03-complete.md

@@ -8,6 +8,7 @@
 - FOCUS on finalizing a lean, LLM-optimized project context
 - ENSURE all critical rules are captured and actionable
 - ABSOLUTELY NO TIME ESTIMATES
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmgd/workflows/3-technical/generate-project-context/workflow.md

@@ -32,6 +32,7 @@ Load config from `{project-root}/_bmad/bmgd/config.yaml` and resolve:
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `game_dev_experience`
 - `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Paths
 

package/src/modules/bmgd/workflows/4-production/code-review/instructions.xml

@@ -12,6 +12,7 @@
   <critical>Read EVERY file in the File List - verify implementation against story requirements</critical>
   <critical>Tasks marked complete but not done = CRITICAL finding</critical>
   <critical>Acceptance Criteria not implemented = HIGH severity finding</critical>
+  <critical>Do not review files that are not part of the application's source code. Always exclude the _bmad/ and _bmad-output/ folders from the review. Always exclude IDE and CLI configuration folders like .cursor/ and .windsurf/ and .claude/</critical>
 
   <step n="1" goal="Load story and discover changes">
     <action>Use provided {{story_path}} or ask user which story file to review</action>

package/src/modules/bmgd/workflows/4-production/code-review/workflow.yaml

@@ -12,7 +12,7 @@ user_skill_level: "{config_source}:user_skill_level"
 document_output_language: "{config_source}:document_output_language"
 date: system-generated
 implementation_artifacts: "{config_source}:implementation_artifacts"
-sprint_status: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+sprint_status: "{implementation_artifacts}/sprint-status.yaml"
 
 # Workflow components
 installed_path: "{project-root}/_bmad/bmgd/workflows/4-production/code-review"

package/src/modules/bmgd/workflows/4-production/correct-course/workflow.yaml

@@ -11,7 +11,7 @@ user_skill_level: "{config_source}:user_skill_level"
 document_output_language: "{config_source}:document_output_language"
 date: system-generated
 implementation_artifacts: "{config_source}:implementation_artifacts"
-sprint_status: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+sprint_status: "{implementation_artifacts}/sprint-status.yaml"
 
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version

package/src/modules/bmgd/workflows/4-production/create-story/checklist.md

@@ -33,7 +33,7 @@ This is a COMPETITION to create the **ULTIMATE story context** that makes LLM de
 
 ### **When Running from Create-Story Workflow:**
 
-- The `{project_root}/_bmad/core/tasks/validate-workflow.xml` framework will automatically:
+- The `{project-root}/_bmad/core/tasks/validate-workflow.xml` framework will automatically:
   - Load this checklist file
   - Load the newly created story file (`{story_file_path}`)
   - Load workflow variables from `{installed_path}/workflow.yaml`
@@ -63,7 +63,7 @@ You will systematically re-do the entire story creation process, but with a crit
 
 1. **Load the workflow configuration**: `{installed_path}/workflow.yaml` for variable inclusion
 2. **Load the story file**: `{story_file_path}` (provided by user or discovered)
-3. **Load validation framework**: `{project_root}/_bmad/core/tasks/validate-workflow.xml`
+3. **Load validation framework**: `{project-root}/_bmad/core/tasks/validate-workflow.xml`
 4. **Extract metadata**: epic_num, story_num, story_key, story_title from story file
 5. **Resolve all workflow variables**: story_dir, output_folder, epics_file, architecture_file, etc.
 6. **Understand current status**: What story implementation guidance is currently provided?

package/src/modules/bmgd/workflows/4-production/create-story/workflow.yaml

@@ -19,7 +19,7 @@ validation: "{installed_path}/checklist.md"
 
 # Variables and inputs
 variables:
-  sprint_status: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Primary source for story tracking
+  sprint_status: "{implementation_artifacts}/sprint-status.yaml || {implementation_artifacts}/sprint-status.yaml" # Primary source for story tracking
   epics_file: "{output_folder}/epics.md" # Preferred source for epic/story breakdown
   prd_file: "{output_folder}/PRD.md" # Fallback for requirements
   architecture_file: "{planning_artifacts}/architecture.md" # Optional architecture context

package/src/modules/bmgd/workflows/4-production/dev-story/workflow.yaml

@@ -16,7 +16,7 @@ story_file: "" # Explicit story path; auto-discovered if empty
 # Context file uses same story_key as story file (e.g., "1-2-user-authentication.context.xml")
 context_file: "{story_dir}/{{story_key}}.context.xml"
 implementation_artifacts: "{config_source}:implementation_artifacts"
-sprint_status: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+sprint_status: "{implementation_artifacts}/sprint-status.yaml || {implementation_artifacts}/sprint-status.yaml"
 
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version

package/src/modules/bmgd/workflows/4-production/retrospective/workflow.yaml

@@ -54,7 +54,7 @@ input_file_patterns:
     load_strategy: "INDEX_GUIDED"
 
 # Required files
-sprint_status_file: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+sprint_status_file: "{implementation_artifacts}/sprint-status.yaml || {implementation_artifacts}/sprint-status.yaml"
 story_directory: "{implementation_artifacts}"
 retrospectives_folder: "{implementation_artifacts}"
 

package/src/modules/bmgd/workflows/4-production/sprint-status/workflow.yaml

@@ -18,14 +18,14 @@ instructions: "{installed_path}/instructions.md"
 
 # Inputs
 variables:
-  sprint_status_file: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+  sprint_status_file: "{implementation_artifacts}/sprint-status.yaml || {implementation_artifacts}/sprint-status.yaml"
   tracking_system: "file-system"
 
 # Smart input file references
 input_file_patterns:
   sprint_status:
     description: "Sprint status file generated by sprint-planning"
-    whole: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+    whole: "{implementation_artifacts}/sprint-status.yaml || {implementation_artifacts}/sprint-status.yaml"
     load_strategy: "FULL_LOAD"
 
 # Standalone so IDE commands get generated

package/src/modules/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml

@@ -23,7 +23,7 @@ checklist: "{installed_path}/checklist.md"
 # Related workflows
 quick_prototype_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
 party_mode_exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+advanced_elicitation: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
 
 # Routing resources (lazy-loaded)
 workflow_init: "{project-root}/_bmad/bmgd/workflows/workflow-status/init/workflow.yaml"

package/src/modules/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml

@@ -23,7 +23,7 @@ checklist: "{installed_path}/checklist.md"
 # Related workflows
 quick_dev_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml"
 party_mode_exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+advanced_elicitation: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
 
 # Game-specific references
 gdd_patterns:

package/src/modules/bmgd/workflows/bmgd-quick-flow/{create-tech-spec → quick-spec}/workflow.yaml

@@ -1,5 +1,5 @@
 # Quick-Flow: Create Tech-Spec (Game Development)
-name: create-tech-spec
+name: quick-spec
 description: "Conversational spec engineering for games - ask questions, investigate code, produce implementation-ready tech-spec."
 author: "BMad"
 
@@ -14,14 +14,14 @@ user_skill_level: "{config_source}:game_dev_experience"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec"
+installed_path: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-spec"
 instructions: "{installed_path}/instructions.md"
 
 # Related workflows
 quick_dev_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml"
 quick_prototype_workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
 party_mode_exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-advanced_elicitation: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+advanced_elicitation: "{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml"
 
 standalone: true
 web_bundle: false

package/src/modules/bmgd/workflows/workflow-status/paths/quickflow-brownfield.yaml

@@ -11,10 +11,10 @@ phases:
     name: "Planning"
     required: true
     workflows:
-      - id: "create-tech-spec"
+      - id: "quick-spec"
         required: true
         agent: "game-solo-dev"
-        command: "create-tech-spec"
+        command: "quick-spec"
         output: "Technical specification"
         note: "Define changes for existing codebase"
 

package/src/modules/bmm/agents/analyst.agent.yaml

@@ -7,13 +7,14 @@ agent:
     title: Business Analyst
     icon: 📊
     module: bmm
+    hasSidecar: false
 
   persona:
     role: Strategic Business Analyst + Requirements Expert
     identity: Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.
-    communication_style: "Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark 'aha!' moments while structuring insights with precision."
+    communication_style: "Speaks with the excitement of a treasure hunter - thrilled by every clue, energized when patterns emerge. Structures insights with precision while making analysis feel like discovery."
     principles: |
-      - Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence.
+      - Channel expert business analysis frameworks: draw upon Porter's Five Forces, SWOT analysis, root cause analysis, and competitive intelligence methodologies to uncover what others miss. Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence.
       - Articulate requirements with absolute precision. Ensure all stakeholder voices heard.
       - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 

package/src/modules/bmm/agents/architect.agent.yaml

@@ -7,12 +7,14 @@ agent:
     title: Architect
     icon: 🏗️
     module: bmm
+    hasSidecar: false
 
   persona:
     role: System Architect + Technical Design Leader
     identity: Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.
-    communication_style: "Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Champions boring technology that actually works."
+    communication_style: "Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.'"
     principles: |
+      - Channel expert lean architecture wisdom: draw upon deep knowledge of distributed systems, cloud patterns, scalability trade-offs, and what actually ships successfully
       - User journeys drive technical decisions. Embrace boring technology for stability.
       - Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact.
       - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`