diff --git a/bmad-core/agents/analyst.md b/bmad-core/agents/analyst.md index 2ae50196..5825b39f 100644 --- a/bmad-core/agents/analyst.md +++ b/bmad-core/agents/analyst.md @@ -1,9 +1,9 @@ # analyst -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/bmad-core/agents/architect.md b/bmad-core/agents/architect.md index 608b7134..1d7c80af 100644 --- a/bmad-core/agents/architect.md +++ b/bmad-core/agents/architect.md @@ -1,9 +1,9 @@ # architect -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/bmad-core/agents/bmad-master.md b/bmad-core/agents/bmad-master.md index 41a513e7..9e574981 100644 --- a/bmad-core/agents/bmad-master.md +++ b/bmad-core/agents/bmad-master.md @@ -1,9 +1,9 @@ # BMad Master -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Greet the user with your name and role, and inform of the *help command. diff --git a/bmad-core/agents/bmad-orchestrator.md b/bmad-core/agents/bmad-orchestrator.md index b215c489..a60d14ce 100644 --- a/bmad-core/agents/bmad-orchestrator.md +++ b/bmad-core/agents/bmad-orchestrator.md @@ -1,9 +1,9 @@ # BMad Web Orchestrator -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows diff --git a/bmad-core/agents/dev.md b/bmad-core/agents/dev.md index f7f190c6..6fb905c9 100644 --- a/bmad-core/agents/dev.md +++ b/bmad-core/agents/dev.md @@ -1,9 +1,9 @@ # dev -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Announce: Greet the user with your name and role, and inform of the *help command. diff --git a/bmad-core/agents/pm.md b/bmad-core/agents/pm.md index c282df89..590940f8 100644 --- a/bmad-core/agents/pm.md +++ b/bmad-core/agents/pm.md @@ -1,9 +1,9 @@ # pm -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/bmad-core/agents/po.md b/bmad-core/agents/po.md index b9bbb0de..38cf278c 100644 --- a/bmad-core/agents/po.md +++ b/bmad-core/agents/po.md @@ -1,9 +1,9 @@ # po -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/bmad-core/agents/qa.md b/bmad-core/agents/qa.md index a74787fd..5921dd97 100644 --- a/bmad-core/agents/qa.md +++ b/bmad-core/agents/qa.md @@ -1,9 +1,9 @@ # qa -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/bmad-core/agents/sm.md b/bmad-core/agents/sm.md index 3785f087..1a4bbbbf 100644 --- a/bmad-core/agents/sm.md +++ b/bmad-core/agents/sm.md @@ -1,9 +1,9 @@ # sm -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/bmad-core/agents/ux-expert.md b/bmad-core/agents/ux-expert.md index 84def70c..ffc0e21f 100644 --- a/bmad-core/agents/ux-expert.md +++ b/bmad-core/agents/ux-expert.md @@ -1,9 +1,9 @@ # ux-expert -CRITICAL: Read the full YAML to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: +CRITICAL: Read the full YAML BLOCK the FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/bmad-core/core-config.yaml b/bmad-core/core-config.yaml index d3fd640c..69c8c7ec 100644 --- a/bmad-core/core-config.yaml +++ b/bmad-core/core-config.yaml @@ -1,4 +1,4 @@ -version: 4.27.0 +version: 4.28.0 markdownExploder: true prd: prdFile: docs/prd.md diff --git a/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.md b/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.md index 727be90b..59993746 100644 --- a/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.md +++ b/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.md @@ -3,7 +3,7 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.md b/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.md index e1cc02ca..3ef5bb10 100644 --- a/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.md +++ b/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.md @@ -3,7 +3,7 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.md b/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.md index 2f387695..f02b178f 100644 --- a/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.md +++ b/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.md @@ -3,7 +3,7 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/expansion-packs/bmad-2d-phaser-game-dev/config.yaml b/expansion-packs/bmad-2d-phaser-game-dev/config.yaml index ff01f965..7d008d7f 100644 --- a/expansion-packs/bmad-2d-phaser-game-dev/config.yaml +++ b/expansion-packs/bmad-2d-phaser-game-dev/config.yaml @@ -1,5 +1,5 @@ name: bmad-2d-phaser-game-dev -version: 1.8.0 +version: 1.9.0 short-title: 2D game development with Phaser 3 & TypeScript description: >- 2D Game Development expansion pack for BMad Method - Phaser 3 & TypeScript diff --git a/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.md b/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.md index ba687dad..c3961818 100644 --- a/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.md +++ b/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.md @@ -3,7 +3,7 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/expansion-packs/bmad-creator-tools/config.yaml b/expansion-packs/bmad-creator-tools/config.yaml index 43722302..d1ab537f 100644 --- a/expansion-packs/bmad-creator-tools/config.yaml +++ b/expansion-packs/bmad-creator-tools/config.yaml @@ -1,6 +1,6 @@ name: bmad-creator-tools -version: 1.7.0 +version: 1.8.0 short-title: Tools for creating BMad framework components description: Tools for creating and extending BMad framework components. author: Brian (BMad) -slashPrefix: bmadCreator \ No newline at end of file +slashPrefix: bmadCreator diff --git a/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.md b/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.md index 880815ab..bd92bc2d 100644 --- a/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.md +++ b/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.md @@ -3,7 +3,7 @@ CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode: ```yaml -IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. +IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}, type=folder (tasks/templates/checklists/data/utils), name=file-name. For example if dependencies.tasks includes create-doc.md, this means you would use `{root}/tasks/create-doc.md`. REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match. activation-instructions: - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER! diff --git a/expansion-packs/bmad-infrastructure-devops/config.yaml b/expansion-packs/bmad-infrastructure-devops/config.yaml index ceedd3d7..0d47e05c 100644 --- a/expansion-packs/bmad-infrastructure-devops/config.yaml +++ b/expansion-packs/bmad-infrastructure-devops/config.yaml @@ -1,5 +1,5 @@ name: bmad-infrastructure-devops -version: 1.7.0 +version: 1.8.0 short-title: Infrastructure and DevOps capabilities description: >- This expansion pack extends BMad Method with comprehensive infrastructure and