Merge branch 'main' into bmgd-fixes

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "6.0.0-alpha.17",
+  "version": "6.0.0-alpha.19",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "6.0.0-alpha.17",
+      "version": "6.0.0-alpha.19",
       "license": "MIT",
       "dependencies": {
         "@kayvan/markdown-tree-parser": "^1.6.1",
@@ -98,6 +98,7 @@
       "integrity": "sha512-yDBHV9kQNcr2/sUr9jghVyz9C3Y5G2zUM2H2lo+9mKv4sFgbA8s8Z9t8D1jiTkGoO/NoIfKMyKWr4s6CN23ZwQ==",
       "dev": true,
       "license": "MIT",
+      "peer": true,
       "dependencies": {
         "@ampproject/remapping": "^2.2.0",
         "@babel/code-frame": "^7.27.1",
@@ -1840,6 +1841,7 @@
       "integrity": "sha512-aPTXCrfwnDLj4VvXrm+UUCQjNEvJgNA8s5F1cvwQU+3KNltTOkBm1j30uNLyqqPNe7gE3KFzImYoZEfLhp4Yow==",
       "devOptional": true,
       "license": "MIT",
+      "peer": true,
       "dependencies": {
         "undici-types": "~7.10.0"
       }
@@ -2156,6 +2158,7 @@
       "integrity": "sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==",
       "dev": true,
       "license": "MIT",
+      "peer": true,
       "bin": {
         "acorn": "bin/acorn"
       },
@@ -2517,6 +2520,7 @@
         }
       ],
       "license": "MIT",
+      "peer": true,
       "dependencies": {
         "caniuse-lite": "^1.0.30001735",
         "electron-to-chromium": "^1.5.204",
@@ -3406,6 +3410,7 @@
       "integrity": "sha512-RNCHRX5EwdrESy3Jc9o8ie8Bog+PeYvvSR8sDGoZxNFTvZ4dlxUB3WzQ3bQMztFrSRODGrLLj8g6OFuGY/aiQg==",
       "dev": true,
       "license": "MIT",
+      "peer": true,
       "dependencies": {
         "@eslint-community/eslint-utils": "^4.2.0",
         "@eslint-community/regexpp": "^4.12.1",
@@ -7493,6 +7498,7 @@
       "integrity": "sha512-I7AIg5boAr5R0FFtJ6rCfD+LFsWHp81dolrFD8S79U9tb8Az2nGrJncnMSnys+bpQJfRUzqs9hnA81OAA3hCuQ==",
       "dev": true,
       "license": "MIT",
+      "peer": true,
       "bin": {
         "prettier": "bin/prettier.cjs"
       },
@@ -8325,6 +8331,7 @@
       "integrity": "sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==",
       "dev": true,
       "license": "MIT",
+      "peer": true,
       "engines": {
         "node": ">=12"
       },

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

@@ -43,7 +43,7 @@ agent:
       triggers:
         - party-mode:
             - input: SPM or fuzzy match start party mode
-            - route: "{project-root}/_bmad/core/workflows/edit-agent/workflow.md"
+            - route: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
             - data: what is being discussed or suggested with the command, along with custom party custom agents if specified
             - type: exec
         - expert-chat:

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

@@ -10,13 +10,12 @@ agent:
 
   persona:
     role: Elite Full-Stack Developer + Quick Flow Specialist
-    identity: Barry is an elite developer who thrives on autonomous execution. He lives and breathes the BMAD Quick Flow workflow, taking projects from concept to deployment with ruthless efficiency. No handoffs, no delays - just pure, focused development. He architects specs, writes the code, and ships features faster than entire teams.
+    identity: Barry handles Quick Flow - from tech spec creation through implementation. Minimum ceremony, lean artifacts, ruthless efficiency.
-    communication_style: "Direct, confident, and implementation-focused. Uses tech slang and gets straight to the point. No fluff, just results. Every response moves the project forward."
+    communication_style: "Direct, confident, and implementation-focused. Uses tech slang (e.g., refactor, patch, extract, spike) and gets straight to the point. No fluff, just results. Stays focused on the task at hand."
     principles: |
-      - Planning and execution are two sides of the same coin. Quick Flow is my religion.
+      - Planning and execution are two sides of the same coin.
       - Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't.
-      - Documentation happens alongside development, not after. Ship early, ship often.
+      - If `**/project-context.md` exists, follow it. If absent, proceed without.
-      - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md ``
 
   menu:
     - trigger: create-tech-spec
@@ -27,10 +26,6 @@ agent:
       workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
       description: Implement the tech spec end-to-end solo (Core of Quick Flow)
 
-    - trigger: code-review
-      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
-      description: Review code and improve it (Highly Recommended, use fresh context and different LLM for best results)
-
     - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: Bring in other experts when I need specialized backup

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

@@ -32,9 +32,12 @@ agent:
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
       description: Create Story (Required to prepare stories for development)
 
-    - trigger: validate-create-story
+    # TODO: validate-create-story is not yet implemented
-      validate-workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
+    # The validate-workflow: handler type is not recognized by the workflow engine
-      description: Validate Story (Highly Recommended, use fresh context and different LLM for best results)
+    # See: https://github.com/bmad-code-org/BMAD-METHOD/issues/1075
+    # - trigger: validate-create-story
+    #   workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/validate-workflow.yaml"
+    #   description: Validate Story (Highly Recommended, use fresh context and different LLM for best results)
 
     - trigger: epic-retrospective
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"

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

@@ -54,7 +54,7 @@ agent:
       description: Create clear technical explanations with examples
 
     - trigger: standards-guide
-      action: "Display the complete documentation standards from {project-root}/_bmadbmm/data/documentation-standards.md in a clear, formatted way for the user."
+      action: "Display the complete documentation standards from {project-root}/_bmad/bmm/data/documentation-standards.md in a clear, formatted way for the user."
       description: Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)
 
     - trigger: party-mode

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

@@ -27,9 +27,12 @@ agent:
       exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
       description: Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture)
 
-    - trigger: validate-design
+    # TODO: validate-design is not yet implemented
-      validate-workflow: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml"
+    # The validate-workflow: handler type is not recognized by the workflow engine
-      description: Validate UX Specification and Design Artifacts
+    # See: https://github.com/bmad-code-org/BMAD-METHOD/issues/1075
+    # - trigger: validate-design
+    #   workflow: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/validate-workflow.yaml"
+    #   description: Validate UX Specification and Design Artifacts
 
     - trigger: create-excalidraw-wireframe
       workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml"

src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md

@@ -3,7 +3,7 @@ name: 'step-01-init'
 description: 'Initialize the product brief workflow by detecting continuation state and setting up the document'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01-init.md'

src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-01b-continue.md

@@ -3,7 +3,7 @@ name: 'step-01b-continue'
 description: 'Resume the product brief workflow from where it was left off, ensuring smooth continuation'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01b-continue.md'

src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-02-vision.md

@@ -3,7 +3,7 @@ name: 'step-02-vision'
 description: 'Discover and define the core product vision, problem statement, and unique value proposition'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-02-vision.md'

src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md

@@ -3,7 +3,7 @@ name: 'step-03-users'
 description: 'Define target users with rich personas and map their key interactions with the product'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-users.md'

src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md

@@ -3,7 +3,7 @@ name: 'step-04-metrics'
 description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-04-metrics.md'

src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md

@@ -3,7 +3,7 @@ name: 'step-05-scope'
 description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-05-scope.md'

src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md

@@ -3,7 +3,7 @@ name: 'step-06-complete'
 description: 'Complete the product brief workflow, update status files, and suggest next steps for the project'
 
 # Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/product-brief'
+workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-complete.md'

src/modules/bmm/workflows/1-analysis/create-product-brief/workflow.md

@@ -55,4 +55,4 @@ Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve
 
 ### 2. First Step EXECUTION
 
-Load, read the full file and then execute `{project-root}/_bmad/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md` to begin the workflow.
+Load, read the full file and then execute `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.

src/modules/bmm/workflows/4-implementation/create-story/instructions.xml

@@ -334,18 +334,8 @@
 
       **Next Steps:**
       1. Review the comprehensive story in {{story_file}}
-      2. **Optional Quality Competition:** Run the scrum masters `*validate-create-story` to have a fresh LLM systematically review and
+      2. Run dev agents `dev-story` for optimized implementation
-      improve the story context
+      3. Run `code-review` when complete (auto-marks done)
-      3. Run dev agents `dev-story` for optimized implementation
-      4. Run `code-review` when complete (auto-marks done)
-
-      **Quality Competition Option:** The `*validate-create-story` command runs the story context through an independent LLM in fresh
-      context that will:
-      - Systematically re-analyze all source documents
-      - Identify any misses, omissions, or improvements
-      - Compete to create a more comprehensive story context
-      - Present findings interactively for your approval
-      - Apply improvements to create the ultimate developer implementation guide
 
       **The developer now has everything needed for flawless implementation!**
     </output>

src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml

@@ -17,7 +17,7 @@
       <action>Use {{story_path}} directly</action>
       <action>Read COMPLETE story file</action>
       <action>Extract story_key from filename or metadata</action>
-      <goto> anchor with id task_check</goto>
+      <goto anchor="task_check" />
     </check>
 
     <!-- Sprint-based story discovery -->