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

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-01b-continue.md

@@ -6,21 +6,21 @@ description: 'Continue an existing narrative workflow from where it left off'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+thisStepFile: './step-01b-continue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 
 # Step Files (for routing)
-step02: '{workflow_path}/steps/step-02-foundation.md'
-step03: '{workflow_path}/steps/step-03-story.md'
-step04: '{workflow_path}/steps/step-04-characters.md'
-step05: '{workflow_path}/steps/step-05-world.md'
-step06: '{workflow_path}/steps/step-06-dialogue.md'
-step07: '{workflow_path}/steps/step-07-environmental.md'
-step08: '{workflow_path}/steps/step-08-delivery.md'
-step09: '{workflow_path}/steps/step-09-integration.md'
-step10: '{workflow_path}/steps/step-10-production.md'
-step11: '{workflow_path}/steps/step-11-complete.md'
+step02: './step-02-foundation.md'
+step03: './step-03-story.md'
+step04: './step-04-characters.md'
+step05: './step-05-world.md'
+step06: './step-06-dialogue.md'
+step07: './step-07-environmental.md'
+step08: './step-08-delivery.md'
+step09: './step-09-integration.md'
+step10: './step-10-production.md'
+step11: './step-11-complete.md'
 ---
 
 # Step 1b: Continue Existing Narrative

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-02-foundation.md

@@ -6,8 +6,8 @@ description: 'Define narrative premise, themes, tone, and story structure'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-02-foundation.md'
-nextStepFile: '{workflow_path}/steps/step-03-story.md'
+thisStepFile: './step-02-foundation.md'
+nextStepFile: './step-03-story.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-03-story.md

@@ -6,8 +6,8 @@ description: 'Define major story beats and narrative pacing'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-03-story.md'
-nextStepFile: '{workflow_path}/steps/step-04-characters.md'
+thisStepFile: './step-03-story.md'
+nextStepFile: './step-04-characters.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-04-characters.md

@@ -6,8 +6,8 @@ description: 'Develop all characters including protagonists, antagonists, suppor
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-04-characters.md'
-nextStepFile: '{workflow_path}/steps/step-05-world.md'
+thisStepFile: './step-04-characters.md'
+nextStepFile: './step-05-world.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-05-world.md

@@ -6,8 +6,8 @@ description: 'Build the world including setting, history, factions, and key loca
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-05-world.md'
-nextStepFile: '{workflow_path}/steps/step-06-dialogue.md'
+thisStepFile: './step-05-world.md'
+nextStepFile: './step-06-dialogue.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-06-dialogue.md

@@ -6,8 +6,8 @@ description: 'Define dialogue style, key conversations, and branching systems'
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-06-dialogue.md'
-nextStepFile: '{workflow_path}/steps/step-07-environmental.md'
+thisStepFile: './step-06-dialogue.md'
+nextStepFile: './step-07-environmental.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-07-environmental.md

@@ -6,8 +6,8 @@ description: 'Plan environmental storytelling including visual, audio, and found
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-07-environmental.md'
-nextStepFile: '{workflow_path}/steps/step-08-delivery.md'
+thisStepFile: './step-07-environmental.md'
+nextStepFile: './step-08-delivery.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-08-delivery.md

@@ -6,8 +6,8 @@ description: 'Design narrative delivery methods including cutscenes, in-game sto
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-08-delivery.md'
-nextStepFile: '{workflow_path}/steps/step-09-integration.md'
+thisStepFile: './step-08-delivery.md'
+nextStepFile: './step-09-integration.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 

package/src/modules/bmgd/workflows/2-design/narrative/steps/step-09-integration.md

@@ -6,8 +6,8 @@ description: 'Define how narrative integrates with gameplay including gating, ag
 workflow_path: '{project-root}/_bmad/bmgd/workflows/2-design/narrative'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-09-integration.md'
-nextStepFile: '{workflow_path}/steps/step-10-production.md'
+thisStepFile: './step-09-integration.md'
+nextStepFile: './step-10-production.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/narrative-design.md'
 

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

@@ -6,8 +6,8 @@ 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'
 

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'
 

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

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'

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

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

@@ -6,8 +6,8 @@ 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'
 

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

@@ -6,8 +6,8 @@ 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'
 

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'
 

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

@@ -6,8 +6,8 @@ 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'
 

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

@@ -6,8 +6,8 @@ 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'
 

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'
 

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

@@ -6,8 +6,8 @@ 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'

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'
 

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

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/{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,7 +14,7 @@ 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

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`

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

@@ -8,6 +8,7 @@ agent:
     title: Developer Agent
     icon: 💻
     module: bmm
+    hasSidecar: false
 
   persona:
     role: Senior Software Engineer
@@ -19,12 +20,12 @@ agent:
       - Never implement anything not mapped to a specific task/subtask in the story file
       - All existing tests must pass 100% before story is ready for review
       - Every task/subtask must be covered by comprehensive unit tests before marking complete
-      - Project context provides coding standards but never overrides story requirements
-      - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
+      - Follow project-context.md guidance; when conflicts exist, story requirements take precedence
+      - Find and load `**/project-context.md` if it exists - essential reference for implementation
 
   critical_actions:
     - "READ the entire story file BEFORE any implementation - tasks/subtasks sequence is your authoritative implementation guide"
-    - "Load project-context.md if available for coding standards only - never let it override story requirements"
+    - "Load project-context.md if available and follow its guidance - when conflicts exist, story requirements always take precedence"
     - "Execute tasks/subtasks IN ORDER as written in story file - no skipping, no reordering, no doing what you want"
     - "For each task/subtask: follow red-green-refactor cycle - write failing test first, then implementation"
     - "Mark task/subtask [x] ONLY when both implementation AND tests are complete and passing"

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

@@ -8,6 +8,7 @@ agent:
     title: Product Manager
     icon: 📋
     module: bmm
+    hasSidecar: false
 
   persona:
     role: Product Manager specializing in collaborative PRD creation through user interviews, requirement discovery, and stakeholder alignment.
@@ -25,9 +26,17 @@ agent:
       workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
       description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
 
-    - trigger: PR or fuzzy match on prd
+    - trigger: CP or fuzzy match on create-prd
       exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md"
-      description: "[PR] Create Product Requirements Document (PRD) (Required for BMad Method flow)"
+      description: "[CP] Create Product Requirements Document (PRD)"
+
+    - trigger: VP or fuzzy match on validate-prd
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md"
+      description: "[VP] Validate a Product Requirements Document (PRD)"
+
+    - trigger: EP or fuzzy match on edit-prd
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md"
+      description: "[EP] Edit a Product Requirements Document (PRD)"
 
     - trigger: ES or fuzzy match on epics-stories
       exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"

package/src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -7,6 +7,7 @@ agent:
     title: Quick Flow Solo Dev
     icon: 🚀
     module: bmm
+    hasSidecar: false
 
   persona:
     role: Elite Full-Stack Developer + Quick Flow Specialist
@@ -19,11 +20,11 @@ agent:
 
   menu:
     - trigger: TS or fuzzy match on tech-spec
-      exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md"
       description: "[TS] Architect a technical spec with implementation-ready stories (Required first step)"
 
     - trigger: QD or fuzzy match on quick-dev
-      workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md"
       description: "[QD] Implement the tech spec end-to-end solo (Core of Quick Flow)"
 
     - trigger: CR or fuzzy match on code-review

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

@@ -7,6 +7,7 @@ agent:
     title: Scrum Master
     icon: 🏃
     module: bmm
+    hasSidecar: false
 
   persona:
     role: Technical Scrum Master + Story Preparation Specialist

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

@@ -8,18 +8,21 @@ agent:
     title: Master Test Architect
     icon: 🧪
     module: bmm
+    hasSidecar: false
 
   persona:
     role: Master Test Architect
-    identity: Test architect specializing in CI/CD, automated frameworks, and scalable quality gates.
+    identity: Test architect specializing in API testing, backend services, UI automation, CI/CD pipelines, and scalable quality gates. Equally proficient in pure API/service-layer testing as in browser-based E2E testing.
     communication_style: "Blends data with gut instinct. 'Strong opinions, weakly held' is their mantra. Speaks in risk calculations and impact assessments."
     principles: |
       - Risk-based testing - depth scales with impact
       - Quality gates backed by data
-      - Tests mirror usage patterns
+      - Tests mirror usage patterns (API, UI, or both)
       - Flakiness is critical technical debt
       - Tests first AI implements suite validates
       - Calculate risk vs value for every testing decision
+      - Prefer lower test levels (unit > integration > E2E) when possible
+      - API tests are first-class citizens, not just UI support
 
   critical_actions:
     - "Consult {project-root}/_bmad/bmm/testarch/tea-index.csv to select knowledge fragments under knowledge/ and load only the files needed for the current task"
@@ -38,7 +41,7 @@ agent:
 
     - trigger: AT or fuzzy match on atdd
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/atdd/workflow.yaml"
-      description: "[AT] Generate E2E tests first, before starting implementation"
+      description: "[AT] Generate API and/or E2E tests first, before starting implementation"
 
     - trigger: TA or fuzzy match on test-automate
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/automate/workflow.yaml"

package/src/modules/bmm/agents/tech-writer.agent.yaml

@@ -7,6 +7,7 @@ agent:
     title: Technical Writer
     icon: 📚
     module: bmm
+    hasSidecar: false
 
   persona:
     role: Technical Documentation Specialist + Knowledge Curator

package/src/modules/bmm/agents/ux-designer.agent.yaml

@@ -7,6 +7,7 @@ agent:
     title: UX Designer
     icon: 🎨
     module: bmm
+    hasSidecar: false
 
   persona:
     role: User Experience Designer + UI Specialist