Merge pull request #17 from arvoreeducacao/joaobarros-/-fix-teammate-mcp-zod-compat

fix: pin zod-to-json-schema + add teammate communication prompt

Author: Joao208

package.json

@@ -42,5 +42,10 @@
     "node": ">=20.0.0",
     "pnpm": ">=9.0.0"
   },
+  "pnpm": {
+    "overrides": {
+      "zod-to-json-schema": "~3.24.5"
+    }
+  },
   "packageManager": "pnpm@9.14.4+sha512.c8180b3fbe4e4bca02c94234717896b5529740a6cbadf19fa78254270403ea2f27d4e1d46a08a0f56c89b63dc8ebfd3ee53326da720273794e6200fcf0d184ab"
 }

packages/agent-teams-lead/src/spawner.ts

@@ -297,6 +297,16 @@ export class TeammateSpawner {
       "- Use ONLY the agent-teams-teammate MCP server for task management. Do NOT search for tools via mcp-proxy.",
       "- After completing all your tasks, check one more time for new tasks before finishing.",
       "",
+      "## TEAMMATE COMMUNICATION",
+      "",
+      "You are NOT working alone. Other teammates may depend on your output or you may depend on theirs.",
+      "",
+      "- After completing a task that produces an API contract, interface, or shared type, use send_message to broadcast the exact contract (paths, request/response shapes, field names) to all teammates.",
+      "- Before implementing code that consumes another teammate's output (e.g. frontend calling a backend API), use fetch_messages to check if they shared the contract. If not available yet, wait and retry.",
+      "- When your task has depends_on, always check fetch_messages for context from the dependency task's owner before starting your implementation.",
+      "- Use write_artifact to publish API contracts, schemas, or interface definitions so other teammates can read_artifact to consume them.",
+      "- NEVER assume paths, field names, or response shapes. Always coordinate with the teammate who owns that layer.",
+      "",
       agentInstructions ? `## Agent Instructions\n\n${agentInstructions}` : "",
     ]
       .filter(Boolean)