diff --git a/src/utility/agent-components/handler-validate-workflow.txt b/src/utility/agent-components/handler-validate-workflow.txt
deleted file mode 100644
index aca040550..000000000
--- a/src/utility/agent-components/handler-validate-workflow.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-    <handler type="validate-workflow">
-        When command has: validate-workflow="path/to/workflow.yaml"
-        1. You MUST LOAD the file at: {project-root}/_bmad/core/tasks/validate-workflow.xml
-        2. READ its entire contents and EXECUTE all instructions in that file
-        3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
-        4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
-    </handler>
\ No newline at end of file
diff --git a/src/utility/agent-components/handler-workflow.txt b/src/utility/agent-components/handler-workflow.txt
deleted file mode 100644
index 1be1dcbe5..000000000
--- a/src/utility/agent-components/handler-workflow.txt
+++ /dev/null
@@ -1,10 +0,0 @@
-    <handler type="workflow">
-      When menu item has: workflow="path/to/workflow.yaml":
-
-      1. CRITICAL: Always LOAD {project-root}/_bmad/core/tasks/workflow.xml
-      2. Read the complete file - this is the CORE OS for processing BMAD workflows
-      3. Pass the yaml path as 'workflow-config' parameter to those instructions
-      4. Follow workflow.xml instructions precisely following all steps
-      5. Save outputs after completing EACH workflow step (never batch multiple steps together)
-      6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-    </handler>
\ No newline at end of file