Developers, design writers and preparers can say a commit others wait on as it lands

Without SendMessage, milestone G's developers could report only at their end, so a seat definition the others wait on could not be handed over mid-way. Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
2026-11-09 19:55:31 +01:00
parent 2de011e070
commit 64cdada15a
3 changed files with 7 additions and 3 deletions
@@ -1,7 +1,7 @@
 ---
 name: hq-design-writer
 description: Writes one set of amendments to hq's to-be designs, glossary and playbooks from accepted decisions and a milestone's findings (hq playbook 02, amending a design; playbook 04 step 4), in a worktree on a branch of its own, ready for the review by architectural domain. Writes only in its worktree; never pushes.
-tools: Read, Grep, Glob, Bash, Write, Edit, mcp__mesh__mesh_call, mcp__mesh__mesh_describe, mcp__mesh__mesh_search
+tools: Read, Grep, Glob, Bash, Write, Edit, mcp__mesh__mesh_call, mcp__mesh__mesh_describe, mcp__mesh__mesh_search, SendMessage
 model: opus
 ---

@@ -1,7 +1,7 @@
 ---
 name: mesh-developer
 description: Builds one prepared change of the Novox mesh in local worktrees on a feature branch (hq playbook 07, develop; playbook 08): code and tests, committed locally, never pushed. Starts from the knowledge base and the prepare, and builds only mesh paths.
-tools: Read, Grep, Glob, Bash, Edit, Write, mcp__mesh__mesh_call, mcp__mesh__mesh_describe, mcp__mesh__mesh_search
+tools: Read, Grep, Glob, Bash, Edit, Write, mcp__mesh__mesh_call, mcp__mesh__mesh_describe, mcp__mesh__mesh_search, SendMessage
 model: sonnet
 ---

@@ -50,5 +50,9 @@ end of the handover file the caller named (the subtasks done by label, the head
 order, the findings), and report. A fresh agent continues from that section; work past that point is lost when the
 context runs out.

+**Say a commit others wait on as it lands.** When the handover names a subtask other agents wait on, send its full
+commit id to the lead with `SendMessage` (to `main`) as soon as it is committed, and go on; commit each subtask on its
+own with its label in the subject, so the others can also read it from your worktree.
+
 Report in under 20 lines: per clause or subtask the change (file:line) and its test, that each test failed
 first, the full commit ids, anything the prepare got wrong, and what is left. Glossary words only.
@@ -1,7 +1,7 @@
 ---
 name: mesh-preparer
 description: Prepares one milestone or small fix of the Novox mesh before any code is written (hq playbook 07, the prepare step; playbook 08): what the knowledge base already decides, the mesh path of every interaction the change adds, every file and test it touches, the subtasks and the release order. Read-only but for its prepare file.
-tools: Read, Grep, Glob, Bash, Write, mcp__mesh__mesh_call, mcp__mesh__mesh_describe, mcp__mesh__mesh_search
+tools: Read, Grep, Glob, Bash, Write, mcp__mesh__mesh_call, mcp__mesh__mesh_describe, mcp__mesh__mesh_search, SendMessage
 model: opus
 ---