From 89b408217aa28c0e73a682354bc93e88f1f9820e Mon Sep 17 00:00:00 2001 From: gnekt Date: Mon, 23 Mar 2026 20:39:17 +0100 Subject: [PATCH] Update agents.md to use dispatcher-driven coordination language MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Remove "message board archival" from Librarian responsibilities - Rename "Who to Message for What" → "When to Suggest Another Agent" - Replace "Message to" column with "Suggest" - Move coordination explanation above the table - Update intro line to reflect dispatcher model --- references/agents.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/references/agents.md b/references/agents.md index 043e01b..4933ab7 100644 --- a/references/agents.md +++ b/references/agents.md @@ -1,6 +1,6 @@ # My Brain Is Full - Crew — Agent Directory -This reference is shared across all agents. Every agent knows the others, their responsibilities, and when to contact them. +This reference is shared across all agents. Every agent knows the others, their responsibilities, and when to suggest them to the dispatcher. --- @@ -73,7 +73,7 @@ All agents read `Meta/user-profile.md` for personalization. This file is created **Role**: Vault Health & Quality Assurance **Agent file**: `librarian.md` -**Responsibilities**: Runs periodic audits of the entire vault — detects structural inconsistencies, merges duplicates, fixes broken links, checks frontmatter quality, tracks growth analytics, and produces health reports. Manages message board archival. +**Responsibilities**: Runs periodic audits of the entire vault — detects structural inconsistencies, merges duplicates, fixes broken links, checks frontmatter quality, tracks growth analytics, and produces health reports. **Contact when**: Vault-wide quality issues are suspected. Something seems structurally wrong. Duplicates, broken links, or inconsistent tags are detected. --- @@ -97,10 +97,12 @@ All agents read `Meta/user-profile.md` for personalization. This file is created --- -## Quick Reference: Who to Message for What +## Quick Reference: When to Suggest Another Agent -| Problem | Message to | -|---------|-----------| +When an agent detects work for another agent, it includes a `### Suggested next agent` section in its output. The dispatcher reads this and decides whether to chain the next agent. See `.claude/references/agent-orchestration.md` for the full protocol. + +| Situation | Suggest | +|-----------|---------| | "Don't know where to file this note" | Architect | | "This area/folder doesn't exist" | Architect | | "Tag doesn't exist in taxonomy" | Architect | @@ -115,5 +117,3 @@ All agents read `Meta/user-profile.md` for personalization. This file is created | "Need to find an existing note" | Seeker | | "Cross-reference this with email" | Postman | | "This came from a meeting recording" | Transcriber | - -**How agents coordinate**: Agents do NOT communicate directly. When an agent detects work for another agent, it includes a `### Suggested next agent` section in its output. The dispatcher reads this and decides whether to chain the next agent. See `.claude/references/agent-orchestration.md` for the full protocol.