bmad-method 6.0.0-alpha.19 → 6.0.0-alpha.20

package/src/modules/cis/workflows/design-thinking/instructions.md

@@ -1,7 +1,7 @@
 # Design Thinking Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/design-thinking/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/design-thinking/workflow.yaml</critical>
 <critical>Load and understand design methods from: {design_methods}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

package/src/modules/cis/workflows/innovation-strategy/instructions.md

@@ -1,7 +1,7 @@
 # Innovation Strategy Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/innovation-strategy/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/innovation-strategy/workflow.yaml</critical>
 <critical>Load and understand innovation frameworks from: {innovation_frameworks}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

package/src/modules/cis/workflows/problem-solving/instructions.md

@@ -1,7 +1,7 @@
 # Problem Solving Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project_root}/\_bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project_root}/\_bmad/cis/workflows/problem-solving/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project_root}/_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/_bmad/cis/workflows/problem-solving/workflow.yaml</critical>
 <critical>Load and understand solving methods from: {solving_methods}</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 <critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>

package/test/fixtures/agent-schema/invalid/menu-triggers/compound-invalid-format.agent.yaml

@@ -0,0 +1,24 @@
+# Test: Compound trigger with invalid format
+# Expected: FAIL
+# Error code: custom
+# Error path: agent.menu[0].trigger
+# Error message: agent.menu[].trigger compound format error: invalid compound trigger format
+
+agent:
+  metadata:
+    id: compound-invalid-format
+    name: Invalid Format
+    title: Invalid Format Test
+    icon: 🧪
+
+  persona:
+    role: Test agent
+    identity: Test identity
+    communication_style: Test style
+    principles:
+      - Test principle
+
+  menu:
+    - trigger: TS or tech-spec
+      description: Missing fuzzy match clause
+      action: test

package/test/fixtures/agent-schema/invalid/menu-triggers/compound-mismatched-kebab.agent.yaml

@@ -0,0 +1,24 @@
+# Test: Compound trigger with mismatched kebab portions
+# Expected: FAIL
+# Error code: custom
+# Error path: agent.menu[0].trigger
+# Error message: agent.menu[].trigger compound format error: kebab-case trigger mismatch: "tech-spec" vs "other-thing"
+
+agent:
+  metadata:
+    id: compound-mismatched-kebab
+    name: Mismatched Kebab
+    title: Mismatched Kebab Test
+    icon: 🧪
+
+  persona:
+    role: Test agent
+    identity: Test identity
+    communication_style: Test style
+    principles:
+      - Test principle
+
+  menu:
+    - trigger: TS or tech-spec or fuzzy match on other-thing
+      description: Kebab portions do not match
+      action: test

package/test/fixtures/agent-schema/invalid/menu-triggers/compound-wrong-shortcut.agent.yaml

@@ -0,0 +1,24 @@
+# Test: Compound trigger with wrong shortcut
+# Expected: FAIL
+# Error code: custom
+# Error path: agent.menu[0].trigger
+# Error message: agent.menu[].trigger compound format error: shortcut "XX" does not match expected "TS" for "tech-spec"
+
+agent:
+  metadata:
+    id: compound-wrong-shortcut
+    name: Wrong Shortcut
+    title: Wrong Shortcut Test
+    icon: 🧪
+
+  persona:
+    role: Test agent
+    identity: Test identity
+    communication_style: Test style
+    principles:
+      - Test principle
+
+  menu:
+    - trigger: XX or tech-spec or fuzzy match on tech-spec
+      description: Shortcut does not match kebab trigger
+      action: test

package/test/fixtures/agent-schema/valid/menu-triggers/compound-triggers.agent.yaml

@@ -0,0 +1,30 @@
+# Test: Valid compound triggers
+# Expected: PASS
+
+agent:
+  metadata:
+    id: compound-triggers
+    name: Compound Triggers
+    title: Compound Triggers Test
+    icon: 🧪
+
+  persona:
+    role: Test agent with compound triggers
+    identity: I test compound trigger validation.
+    communication_style: Clear
+    principles:
+      - Test compound format
+
+  menu:
+    - trigger: TS or tech-spec or fuzzy match on tech-spec
+      description: Two-word compound trigger
+      action: tech_spec
+    - trigger: DS or dev-story or fuzzy match on dev-story
+      description: Another two-word compound trigger
+      action: dev_story
+    - trigger: WI or workflow-init-process or fuzzy match on workflow-init-process
+      description: Three-word compound trigger (uses first 2 words for shortcut)
+      action: workflow_init
+    - trigger: H or help or fuzzy match on help
+      description: Single-word compound trigger (1-letter shortcut)
+      action: help