@trygentic/agentloop 0.16.0-alpha.11 → 0.18.0-alpha.11

package/templates/agents/product-manager/product-manager.bt.json

@@ -2,6 +2,7 @@
   "name": "product-manager-continuous-agent-tree",
   "description": "Continuous behavior tree for the Product Manager agent. Loops forever, waiting for agent messages or task assignments (delegation requests from the chat agent). Receives a high-level feature request, creates subprojects, breaks work into tasks, and builds DAG dependencies.",
   "version": "2.0.0",
+  "mode": "reactive",
   "tree": {
     "type": "root",
     "child": {
@@ -19,29 +20,218 @@
           "comment": "Load task details if a real DB task was assigned, or use the request data already on the blackboard (for both agent messages and direct requests)"
         },
         {
-          "type": "llm-action",
-          "name": "PlanAndCreateTasks",
-          "prompt": "You are a product manager agent. Your job is to break down a high-level feature request into actionable AGILE tasks with proper DAG dependencies.\n\n## Feature Request\nTitle: {{taskTitle}}\nDescription: {{taskDescription}}\n\n## CRITICAL: Maximize Parallel Tool Calls\nYou MUST minimize the number of LLM turns by batching independent tool calls into the SAME response.\nEvery extra turn adds ~5-10 seconds of latency. Batch aggressively.\n\n## Your Workflow\n\n### Turn 1 — Gather Context (parallel reads)\nCall BOTH of these tools in a SINGLE response:\n- `mcp__agentloop__list_subprojects` — check for existing subprojects\n- `mcp__agentloop__list_tasks` with `limit: 100, status: \"all\"` — check existing tasks\n\n### Turn 2 — Create Subproject (if needed)\nIf the delegation message included a subprojectId, reuse it. Otherwise call `mcp__agentloop__create_subproject`.\nIf a subproject already exists for this work, skip creation.\nSave the subprojectId for ALL subsequent create_task calls.\nIf tasks already cover this work, report that instead of creating duplicates and stop.\n\n### Turn 3 — Analyze & Create ALL Tasks (SINGLE response)\nDetermine task count based on ACTUAL complexity:\n- Simple (1-5 tasks): \"add logout button\" -> 1-2 tasks\n- Medium (5-15 tasks): \"add user authentication\" -> 8-12 tasks\n- Large (20-30 tasks): \"build payment system\" -> 25-30 tasks\n\nDO NOT inflate task counts artificially.\n\n**IMPORTANT: Call ALL `mcp__agentloop__create_task` tools in a SINGLE response as parallel tool_use blocks.**\nDo NOT create tasks one at a time across multiple turns. Include all of them in one message.\nEach call needs: title, description, priority, tags, sequence, subprojectId.\nRecord all returned task IDs from the results.\n\n### Turn 4 — Add ALL Dependencies (SINGLE response)\n**IMPORTANT: Call ALL `mcp__agentloop__add_task_dependency` tools in a SINGLE response as parallel tool_use blocks.**\nDo NOT add dependencies one at a time across multiple turns.\nUse the task IDs returned from Turn 3. Maximize parallelism — engineers work in isolated worktrees.\n\n### Turn 5 — Validate (parallel reads)\nCall BOTH in a SINGLE response:\n- `mcp__agentloop__validate_dag`\n- `mcp__agentloop__visualize_dag`\n\n## Critical Rules\n- You are a PLANNER, not an implementer. NEVER write code or create files.\n- ALWAYS create tasks using mcp__agentloop__create_task\n- ALWAYS build DAG dependencies using mcp__agentloop__add_task_dependency\n- ALWAYS include subprojectId in every create_task call\n- Engineers work in project root (.) - NEVER include commands that create subdirectories\n- Explicitly specify tech stack in task descriptions\n- NEVER make sequential tool calls when they can be parallel. This is a performance-critical agent.\n\nProvide a summary when done.",
-          "contextKeys": ["taskTitle", "taskDescription", "taskComments"],
-          "subagent": "product-manager",
-          "maxTurns": 25,
-          "outputSchema": {
-            "type": "object",
-            "properties": {
-              "subprojectId": { "type": "number", "description": "ID of the created or reused subproject" },
-              "subprojectName": { "type": "string", "description": "Name of the subproject" },
-              "tasksCreated": { "type": "number", "description": "Number of tasks created" },
-              "taskIds": { "type": "array", "items": { "type": "number" }, "description": "IDs of created tasks" },
-              "dependenciesAdded": { "type": "number", "description": "Number of DAG dependencies added" },
-              "maxParallelism": { "type": "number", "description": "Maximum parallelism achieved in the DAG" },
-              "dagValidated": { "type": "boolean", "description": "Whether DAG validation passed" },
-              "summary": { "type": "string", "description": "Summary of work done" },
-              "complexityLevel": { "type": "string", "enum": ["simple", "medium", "large"], "description": "Assessed complexity level" }
+          "type": "selector",
+          "comment": "Route based on message type: pre-existing bug escalation, existing subproject update, or normal task planning",
+          "children": [
+            {
+              "type": "sequence",
+              "comment": "Handle pre-existing bug escalation from QA agent",
+              "children": [
+                {
+                  "type": "condition",
+                  "call": "IsPreExistingBugEscalation",
+                  "comment": "Check if this is a pre-existing bug escalation message from QA"
+                },
+                {
+                  "type": "llm-action",
+                  "name": "HandlePreExistingBugEscalation",
+                  "allowedTools": [
+                    "mcp__agentloop__list_subprojects",
+                    "mcp__agentloop__list_tasks",
+                    "mcp__agentloop__get_task",
+                    "mcp__agentloop__create_task",
+                    "mcp__agentloop__add_task_dependency",
+                    "mcp__agentloop__pause_subproject",
+                    "mcp__agentloop__resume_subproject",
+                    "mcp__agentloop__reorganize_dag",
+                    "mcp__agentloop__validate_dag",
+                    "mcp__agentloop__send_agent_message"
+                  ],
+                  "prompt": "You are handling a pre-existing bug escalation from QA testing.\n\n## Bug Details\nTitle: {{taskTitle}}\nDetails: {{taskDescription}}\n\n## What Happened\nA QA agent found that testing of an unrelated task is completely blocked by a pre-existing bug.\nThe bug is NOT related to the task's changes - it is a pre-existing issue in the codebase.\n\n## Your Workflow\n\n### Turn 1 - Gather Context (parallel reads)\nCall BOTH tools in a SINGLE response:\n- `mcp__agentloop__list_subprojects` - find the subproject for the blocked task\n- `mcp__agentloop__list_tasks` with `limit: 100` - check for existing tasks that might already address this bug\n\n### Turn 2 - Pause Subproject\nCall `mcp__agentloop__pause_subproject` with:\n- subprojectId: the blocked task's subproject ID (from Turn 1)\n- reason: \"Reorganizing DAG for pre-existing bug fix\"\n- timeoutSeconds: 120\n\nThis prevents the orchestrator from picking up tasks that could conflict with the DAG reorganization.\n\n### Turn 3 - Check for Existing Fix Task\nIf there is already a task to fix this bug, just add a dependency and skip to Turn 5.\nOtherwise, proceed to Turn 4.\n\n### Turn 4 - Create Fix Task\nCall `mcp__agentloop__create_task` with:\n- title: \"Fix pre-existing bug: [brief description]\"\n- description: Include the bug file, error message, and context from the escalation\n- priority: \"high\" (blocking other tasks)\n- assigned_agent: \"engineer\"\n- subprojectId: same as the blocked task's subproject\n- tags: \"bug-fix,pre-existing,blocking\"\n\nRecord the returned task ID.\n\n### Turn 5 - Add Dependency and Reorganize DAG\nCall these in a SINGLE response:\n- `mcp__agentloop__add_task_dependency` - make the blocked task depend on the fix task\n  (dependentTaskId = blocked task ID, prerequisiteTaskId = new fix task ID)\n- `mcp__agentloop__update_task_status` - move the blocked task to 'todo' if it is not already\n- `mcp__agentloop__reorganize_dag` - recalculate execution order\n\n### Turn 6 - Resume Subproject\nALWAYS call `mcp__agentloop__resume_subproject` with the subprojectId, even if previous steps failed.\nFailing to resume will leave the subproject permanently paused and block all future task scheduling.\n\n### Turn 7 - Notify Merge Resolver\nSend a coordination message to the merge-resolver:\n- `mcp__agentloop__send_agent_message` with to: \"merge-resolver\", type: \"coordination\"\n- content: { event: \"prerequisite_fix_created\", fixTaskId, blockedTaskId, bugDescription }\n\n### Turn 8 - Validate\nCall `mcp__agentloop__validate_dag` to ensure no cycles were introduced.\n\nProvide a summary when done.",
+                  "contextKeys": [
+                    "taskTitle",
+                    "taskDescription"
+                  ],
+                  "subagent": "product-manager",
+                  "outputSchema": {
+                    "type": "object",
+                    "properties": {
+                      "fixTaskId": {
+                        "type": "number",
+                        "description": "ID of the created or found fix task"
+                      },
+                      "blockedTaskId": {
+                        "type": "number",
+                        "description": "ID of the blocked task that depends on the fix"
+                      },
+                      "existingFixFound": {
+                        "type": "boolean",
+                        "description": "Whether an existing fix task was found (true) or a new one was created (false)"
+                      },
+                      "dependencyAdded": {
+                        "type": "boolean",
+                        "description": "Whether the dependency was successfully added"
+                      },
+                      "dagValidated": {
+                        "type": "boolean",
+                        "description": "Whether DAG validation passed after changes"
+                      },
+                      "tasksCreated": {
+                        "type": "number",
+                        "description": "Number of tasks created (0 if existing fix found, 1 if new fix created)"
+                      },
+                      "summary": {
+                        "type": "string",
+                        "description": "Summary of actions taken to handle the pre-existing bug"
+                      }
+                    },
+                    "required": [
+                      "tasksCreated",
+                      "summary",
+                      "dagValidated"
+                    ]
+                  },
+                  "outputKey": "pmResult",
+                  "temperature": 0.3
+                }
+              ]
             },
-            "required": ["tasksCreated", "summary", "dagValidated"]
-          },
-          "outputKey": "pmResult",
-          "temperature": 0.3
+            {
+              "type": "sequence",
+              "comment": "Handle update/modification of existing subproject tasks",
+              "children": [
+                {
+                  "type": "condition",
+                  "call": "IsExistingSubprojectUpdate",
+                  "comment": "Check if this message targets an existing subproject for modification"
+                },
+                {
+                  "type": "llm-action",
+                  "name": "UpdateExistingSubprojectTasks",
+                  "allowedTools": [
+                    "mcp__agentloop__get_subproject",
+                    "mcp__agentloop__list_subprojects",
+                    "mcp__agentloop__list_tasks",
+                    "mcp__agentloop__get_task",
+                    "mcp__agentloop__update_task",
+                    "mcp__agentloop__create_task",
+                    "mcp__agentloop__add_task_dependency",
+                    "mcp__agentloop__pause_subproject",
+                    "mcp__agentloop__resume_subproject",
+                    "mcp__agentloop__reorganize_dag",
+                    "mcp__agentloop__validate_dag",
+                    "mcp__agentloop__visualize_dag",
+                    "mcp__agentloop__send_agent_message"
+                  ],
+                  "prompt": "You are updating tasks in an existing subproject based on a user request.\n\n## Request\nTitle: {{taskTitle}}\nDescription: {{taskDescription}}\n\n## CRITICAL: Minimize Tool Call Turns\nBatch independent tool calls in the SAME response.\n\n## Your Workflow\n\n### Turn 1 — Gather Context (parallel reads)\nCall ALL of these in a SINGLE response:\n- `mcp__agentloop__get_subproject` with the subprojectId from the message\n- `mcp__agentloop__list_tasks` with `limit: 100` to see all tasks\n- `mcp__agentloop__list_subprojects` for full context\n\n### Turn 2 — Analyze What Needs to Change\nCompare the user's request against existing tasks in the subproject.\nDetermine:\n- Which existing tasks need modification (title, description, priority changes)\n- Which new tasks need to be created\n- Which existing tasks are now unnecessary and should be deleted/blocked\n- Which dependencies need to change\n\n### Turn 3 — Pause if Active\nIf the subproject has ANY tasks in 'in-progress' or 'done' status:\n- Call `mcp__agentloop__pause_subproject` with reason: \"Updating subproject tasks\" and timeoutSeconds: 120\n\n### Turn 4 — Apply Changes (SINGLE response)\nBatch ALL changes in a SINGLE response:\n- `mcp__agentloop__update_task` for each task that needs modification\n- `mcp__agentloop__create_task` for new tasks (with subprojectId)\n- `mcp__agentloop__update_task_status` to block tasks that are no longer needed\n- `mcp__agentloop__add_task_dependency` for new dependencies\n\n### Turn 5 — Reorganize and Validate (parallel)\nCall in a SINGLE response:\n- `mcp__agentloop__reorganize_dag`\n- `mcp__agentloop__validate_dag`\n- `mcp__agentloop__visualize_dag`\n\n### Turn 6 — Resume and Notify\nCall in a SINGLE response:\n- `mcp__agentloop__resume_subproject` (if paused)\n- `mcp__agentloop__send_agent_message` to merge-resolver if the subproject is active\n\nProvide a summary of all changes made.",
+                  "contextKeys": ["taskTitle", "taskDescription", "taskComments"],
+                  "subagent": "product-manager",
+                  "outputSchema": {
+                    "type": "object",
+                    "properties": {
+                      "subprojectId": { "type": "number" },
+                      "tasksModified": { "type": "number", "description": "Number of existing tasks modified" },
+                      "tasksCreated": { "type": "number", "description": "Number of new tasks created" },
+                      "tasksRemoved": { "type": "number", "description": "Number of tasks blocked/removed" },
+                      "dependenciesChanged": { "type": "number", "description": "Number of dependency changes" },
+                      "dagValidated": { "type": "boolean" },
+                      "summary": { "type": "string" }
+                    },
+                    "required": ["summary", "dagValidated"]
+                  },
+                  "outputKey": "pmResult",
+                  "temperature": 0.3
+                }
+              ]
+            },
+            {
+              "type": "llm-action",
+              "name": "PlanAndCreateTasks",
+              "comment": "Normal task planning - break down feature requests into tasks with DAG dependencies",
+              "allowedTools": [
+                "mcp__agentloop__list_subprojects",
+                "mcp__agentloop__get_subproject",
+                "mcp__agentloop__list_tasks",
+                "mcp__agentloop__get_task",
+                "mcp__agentloop__create_subproject",
+                "mcp__agentloop__create_task",
+                "mcp__agentloop__add_task_dependency",
+                "mcp__agentloop__pause_subproject",
+                "mcp__agentloop__resume_subproject",
+                "mcp__agentloop__validate_dag",
+                "mcp__agentloop__visualize_dag",
+                "mcp__agentloop__reorganize_dag",
+                "mcp__agentloop__send_agent_message"
+              ],
+              "prompt": "You are a product manager agent. Your job is to break down a high-level feature request into actionable AGILE tasks with proper DAG dependencies.\n\n## Feature Request\nTitle: {{taskTitle}}\nDescription: {{taskDescription}}\n\n## CRITICAL: Maximize Parallel Tool Calls\nYou MUST minimize the number of LLM turns by batching independent tool calls into the SAME response.\nEvery extra turn adds ~5-10 seconds of latency. Batch aggressively.\n\n## Your Workflow\n\n### Turn 1 \u2014 Gather Context (parallel reads)\nCall BOTH of these tools in a SINGLE response:\n- `mcp__agentloop__list_subprojects` \u2014 check for existing subprojects\n- `mcp__agentloop__list_tasks` with `limit: 100` \u2014 check existing tasks (omit status to get all)\n\n### Turn 1.5 \u2014 Analyze Existing Subprojects (CRITICAL)\nReview the results from Turn 1. For each existing subproject:\n- Check its name and description against the new work request\n- If tasks already cover this work, report \"Work already planned\" and STOP\n- If the subproject is RELATED to the new work:\n  - Reuse this subproject's ID for new tasks (do NOT create a new subproject)\n  - When adding dependencies, include dependencies on EXISTING tasks in the subproject if appropriate\n  - After adding all tasks and dependencies, call `mcp__agentloop__reorganize_dag`\n\n### Turn 2 \u2014 Create Subproject (if needed)\nIf the delegation message included a subprojectId, reuse it. Otherwise call `mcp__agentloop__create_subproject`.\nIf a subproject already exists for this work (determined in Turn 1.5), skip creation and reuse its ID.\nSave the subprojectId for ALL subsequent create_task calls.\nIf tasks already cover this work, report that instead of creating duplicates and stop.\n\n### Turn 3 \u2014 Analyze & Create ALL Tasks (SINGLE response)\nDetermine task count based on ACTUAL complexity:\n- Simple (1-5 tasks): \"add logout button\" -> 1-2 tasks\n- Medium (5-15 tasks): \"add user authentication\" -> 8-12 tasks\n- Large (20-30 tasks): \"build payment system\" -> 25-30 tasks\n\nDO NOT inflate task counts artificially.\n\n**IMPORTANT: Call ALL `mcp__agentloop__create_task` tools in a SINGLE response as parallel tool_use blocks.**\nDo NOT create tasks one at a time across multiple turns. Include all of them in one message.\nEach call needs: title, description, priority, tags, sequence, subprojectId.\nRecord all returned task IDs from the results.\n\n### Turn 4 \u2014 Add ALL Dependencies (SINGLE response)\n**IMPORTANT: Call ALL `mcp__agentloop__add_task_dependency` tools in a SINGLE response as parallel tool_use blocks.**\nDo NOT add dependencies one at a time across multiple turns.\nUse the task IDs returned from Turn 3. Maximize parallelism \u2014 engineers work in isolated worktrees.\n\n### Turn 4.5 \u2014 Pause if Active Subproject\nIf you are adding tasks to an existing subproject that has ANY tasks in 'in-progress' or 'done' status:\n1. Call `mcp__agentloop__pause_subproject` with reason: \"Adding new tasks and reorganizing DAG\" and timeoutSeconds: 120\n\nIf the subproject has NO active tasks (all todo or none started), skip pause/resume.\n\n### Turn 5 \u2014 Validate and Reorganize\nCall in a SINGLE response:\n- `mcp__agentloop__validate_dag`\n- `mcp__agentloop__visualize_dag`\n- `mcp__agentloop__reorganize_dag` (MANDATORY if tasks were added to an existing subproject)\n\n### Turn 5.5 \u2014 Resume Subproject & Notify Merge Resolver (if paused in Turn 4.5)\nIf you paused the subproject in Turn 4.5, you MUST resume it now.\nCall in a SINGLE response:\n- `mcp__agentloop__resume_subproject` - ALWAYS resume, even if reorganization failed\n- `mcp__agentloop__send_agent_message` with:\n  - to: \"merge-resolver\"\n  - type: \"coordination\"\n  - content: { event: \"subproject_tasks_added\", subprojectId: <id>, newTaskIds: [<ids>], message: \"New tasks added to active subproject. Merge ordering may need adjustment.\" }\n\n**CRITICAL: You MUST call `mcp__agentloop__resume_subproject` if you called `pause_subproject` earlier. Failing to resume will leave the subproject permanently paused.**\n\nIf the subproject was NOT paused (not active), just notify the merge-resolver:\nIf you added tasks to an existing subproject that has any tasks in 'in-progress' or 'done' status:\nCall `mcp__agentloop__send_agent_message` with:\n- to: \"merge-resolver\"\n- type: \"coordination\"\n- content: { event: \"subproject_tasks_added\", subprojectId: <id>, newTaskIds: [<ids>], message: \"New tasks added to active subproject. Merge ordering may need adjustment.\" }\n\n## Critical Rules\n- You are a PLANNER, not an implementer. NEVER write code or create files.\n- ALWAYS create tasks using mcp__agentloop__create_task\n- ALWAYS build DAG dependencies using mcp__agentloop__add_task_dependency\n- ALWAYS include subprojectId in every create_task call\n- Engineers work in project root (.) - NEVER include commands that create subdirectories\n- Explicitly specify tech stack in task descriptions\n- NEVER make sequential tool calls when they can be parallel. This is a performance-critical agent.\n- When adding to an existing subproject, call reorganize_dag AFTER adding tasks and dependencies.\n- Notify merge-resolver when modifying active subprojects (those with in-progress or done tasks).\n\nProvide a summary when done.",
+              "contextKeys": [
+                "taskTitle",
+                "taskDescription",
+                "taskComments"
+              ],
+              "subagent": "product-manager",
+              "outputSchema": {
+                "type": "object",
+                "properties": {
+                  "subprojectId": {
+                    "type": "number",
+                    "description": "ID of the created or reused subproject"
+                  },
+                  "subprojectName": {
+                    "type": "string",
+                    "description": "Name of the subproject"
+                  },
+                  "tasksCreated": {
+                    "type": "number",
+                    "description": "Number of tasks created"
+                  },
+                  "taskIds": {
+                    "type": "array",
+                    "items": {
+                      "type": "number"
+                    },
+                    "description": "IDs of created tasks"
+                  },
+                  "dependenciesAdded": {
+                    "type": "number",
+                    "description": "Number of DAG dependencies added"
+                  },
+                  "maxParallelism": {
+                    "type": "number",
+                    "description": "Maximum parallelism achieved in the DAG"
+                  },
+                  "dagValidated": {
+                    "type": "boolean",
+                    "description": "Whether DAG validation passed"
+                  },
+                  "summary": {
+                    "type": "string",
+                    "description": "Summary of work done"
+                  },
+                  "complexityLevel": {
+                    "type": "string",
+                    "enum": [
+                      "simple",
+                      "medium",
+                      "large"
+                    ],
+                    "description": "Assessed complexity level"
+                  },
+                  "addedToExistingSubproject": {
+                    "type": "boolean",
+                    "description": "Whether tasks were added to an existing subproject vs a new one"
+                  }
+                },
+                "required": [
+                  "tasksCreated",
+                  "summary",
+                  "dagValidated"
+                ]
+              },
+              "outputKey": "pmResult",
+              "temperature": 0.3
+            }
+          ]
         },
         {
           "type": "action",
@@ -50,8 +240,7 @@
         },
         {
           "type": "action",
-          "call": "RequestStatusChange",
-          "comment": "Request task status change to done - PM work is complete"
+          "call": "ReportTriggerPass"
         },
         {
           "type": "action",
@@ -84,7 +273,8 @@
       "agentMessageSender": null,
       "agentMessageType": null,
       "isDirectRequest": false,
-      "isAgentMessage": false
+      "isAgentMessage": false,
+      "isColumnTriggered": false
     }
   }
 }

package/templates/agents/product-manager/product-manager.md

@@ -6,15 +6,18 @@ description: >-
   want to plan sprints, or need task breakdowns.
 instanceCount: 1
 tools:
-  # Base Claude Code tools - planning role, no file access
-  - WebFetch
-  - WebSearch
-  - AskUserQuestion
-  - SlashCommand
+  - read
+  - glob
+  - grep
+  # Base OpenCode tools - planning role, no file access
+  - webfetch
+  - websearch
+  - question
   # MCP tools - agentloop
   - mcp__agentloop__create_task
+  - mcp__agentloop__update_task
   - mcp__agentloop__update_task_status
-  - mcp__agentloop__request_status_change
+  - mcp__agentloop__report_trigger_result
   - mcp__agentloop__get_task
   - mcp__agentloop__list_tasks
   - mcp__agentloop__add_task_comment
@@ -22,10 +25,15 @@ tools:
   - mcp__agentloop__get_parallel_tasks
   - mcp__agentloop__visualize_dag
   - mcp__agentloop__validate_dag
+  - mcp__agentloop__reorganize_dag
+  - mcp__agentloop__send_agent_message
   - mcp__agentloop__create_subproject
   - mcp__agentloop__list_subprojects
   - mcp__agentloop__get_subproject
-model: opus
+  - mcp__agentloop__receive_messages
+  # MCP tools - agentloop subproject pause/resume
+  - mcp__agentloop__pause_subproject
+  - mcp__agentloop__resume_subproject
 mcpServers:
   agentloop:
     # Internal MCP server - handled by the agent worker
@@ -40,7 +48,7 @@ mcp:
         instructions: |
           ALWAYS check existing tasks BEFORE creating new ones.
           Prevents duplicate tasks and builds on existing work.
-          Use limit: 100, status: "all" for full context.
+          Use limit: 100 for full context (omit status to get all tasks).
         required: true
       - name: create_task
         instructions: |
@@ -101,6 +109,42 @@ mcp:
         required: true
       - name: get_subproject
         instructions: Get subproject details including associated tasks and progress.
+      - name: reorganize_dag
+        instructions: |
+          Call AFTER adding tasks or dependencies to an existing subproject.
+          This recalculates sequence numbers based on the updated dependency graph.
+          MANDATORY when inserting tasks into an existing DAG.
+        required: true
+      - name: send_agent_message
+        instructions: |
+          Use to notify the merge-resolver agent when:
+          1. Tasks are added to an active subproject (the merge order may change)
+          2. Dependencies are modified in an active subproject
+          Send coordination messages with event type and relevant task/subproject IDs.
+      - name: update_task
+        instructions: |
+          Use to modify existing tasks when the user requests changes to planned work.
+          Can update: title, description, priority, assigned agent, tags, estimation hours.
+          Use when adding to or modifying an existing subproject's tasks.
+          ONLY modify tasks that need to change - don't touch tasks that are fine as-is.
+      - name: update_task_status
+        instructions: |
+          Use to move tasks back to 'todo' when reorganizing the DAG after
+          pre-existing bug fixes are created as prerequisites.
+      - name: receive_messages
+        instructions: |
+          Check for incoming agent messages. Used to receive coordination
+          messages from other agents, including pre-existing bug escalations
+          from QA agents that need fix tasks created.
+      - name: pause_subproject
+        instructions: |
+          Pause the subproject BEFORE reorganizing the DAG when adding prerequisite tasks.
+          Prevents race conditions where tasks are picked up before dependencies are established.
+          Use timeoutSeconds: 120 (2 minutes) for DAG reorganization.
+      - name: resume_subproject
+        instructions: |
+          Resume the subproject AFTER DAG reorganization is complete.
+          Always resume even if reorganization failed.
 ---
 
 # Product Manager Agent
@@ -147,12 +191,21 @@ ALWAYS explicitly specify the technology stack in task descriptions:
 
 ## Workflow
 
-0. **create_subproject** - Create a subproject using `mcp__agentloop__create_subproject` with a descriptive name and summary of the feature/work being planned. Use `list_subprojects` first to check if a relevant subproject already exists before creating a new one.
-1. **list_tasks** - Check existing tasks first
+0. **list_subprojects** + **list_tasks** - ALWAYS check BOTH before doing anything
+   - Analyze each existing subproject: What is it about? What tasks does it have? What status?
+   - Determine if the new work request relates to ANY existing subproject
+
+0.5. **Route decision** - Based on analysis:
+   - If work fits an existing subproject, add tasks to THAT subproject (don't create a new one)
+   - If work is completely new, create a new subproject
+   - If work spans multiple subprojects, choose the most relevant one, or create a new one
+
+1. **create_subproject** (if needed) - Only create if no existing subproject fits. Use `mcp__agentloop__create_subproject` with a descriptive name and summary.
 2. **create_task** - Create appropriately-sized tasks (record IDs!). Assign all tasks to the subproject using the `subprojectId` parameter.
-3. **add_task_dependency** - MANDATORY: Build DAG structure
-4. **validate_dag** - Ensure no cycles
-5. **visualize_dag** - Show execution levels
+3. **add_task_dependency** - MANDATORY: Build DAG structure. When adding to an existing subproject, include dependencies on existing tasks if appropriate.
+4. **reorganize_dag** - MANDATORY if adding to an existing subproject. Recalculates sequence numbers.
+5. **validate_dag** + **visualize_dag** - Verify no cycles and show execution levels.
+6. **send_agent_message** - Notify merge-resolver if the subproject is active (has in-progress or done tasks).
 
 ## Subproject Management (MANDATORY)
 
@@ -197,6 +250,26 @@ Level 5: [255, 256] Validation, Tests
 Max Parallelism: 3
 ```
 
+## Pre-Existing Bug Escalation Handling
+
+When a QA agent detects a pre-existing bug that blocks testing of an unrelated task, it sends a
+`pre_existing_bug_escalation` coordination message to the product-manager. The PM behavior tree
+automatically routes these messages to the `HandlePreExistingBugEscalation` handler.
+
+**Workflow for pre-existing bug escalations:**
+1. Check for existing tasks that might already fix this bug
+2. If no existing fix task, create a high-priority bug-fix task assigned to an engineer
+3. Add the fix task as a prerequisite of the blocked task (DAG dependency)
+4. Reorganize the DAG to recalculate execution order
+5. Notify the merge-resolver about the new prerequisite
+6. Validate the DAG to ensure no cycles
+
+**Key rules for bug-fix tasks:**
+- Tag with `bug-fix,pre-existing,blocking`
+- Set priority to `high` (they block other work)
+- Place in the same subproject as the blocked task
+- Always add as a prerequisite dependency, not just a sibling task
+
 ## Output Requirements
 
 Include in summary: