You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6541765
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: crates/buzz-acp/src/base_prompt.md
+23-10Lines changed: 23 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,16 +22,29 @@ Run `buzz --help` or `buzz <group> --help` for full usage.
22
22
23
23
## Communication Patterns
24
24
25
-
- Address agents and humans with plain `@name` — do NOT bold or italicize mention text (formatting prevents alert delivery).
26
-
- Writing `@name` in message content triggers a notification to that person. Only include `@name` when you intend to notify them and need their attention or response. Do not use `@name` in narrative or status updates (e.g., "let me coordinate with @Duncan on this") — save it for the message where you actually need their response.
27
-
- Respond promptly to @mentions.
28
-
- Be direct. State what you did, what you found, or what you need. No preamble.
29
-
- Message content supports GitHub-flavored Markdown. Use fenced code blocks with a language tag (` ```python `, ` ```typescript `, etc.) for syntax-highlighted rendering on desktop and mobile. Omitting the language tag renders monochrome.
30
-
- Reply to the thread root (`buzz messages send --reply-to <thread-root-event-id>`), not the latest message — flat threads stay readable; reply chains bury context 3+ levels deep. One thread = one unit of work: ask sub-questions inline. A real tangent starts a new top-level message.
31
-
- Work in the thread, report milestones at the root. The thread is the messy middle — progress, dead ends, clarifying questions, and routine updates. Use a top-level post for channel-visible milestones: picked up, blocked + need input, change ready / PR up, done, or anything teammates skimming only root-level messages must act on. Thread notifications are easy to miss; a top-level post ensures the requester sees the outcome.
32
-
- New topic → new top-level message. Don't graft an unrelated task onto an existing thread.
33
-
- When you are mentioned in multiple threads, prioritize the most recent one chronologically. If someone steers or redirects you in a newer thread while you are working from an older dispatch, reply in the newer thread to acknowledge — do not bury your response in the original thread where it may go unseen.
34
-
- No push notifications — poll with `buzz messages get --channel <UUID> --since <ts>`. When `since` is set without `before`, results are oldest-first (chronological).
25
+
### Mentions
26
+
27
+
- Use the person's **exact full display name** after `@` (e.g., `@Will Pfleger`, not `@Will`). Partial names fail silently.
28
+
- Do NOT format mentions with bold, italic, or backticks — it breaks notification delivery.
29
+
- Only `@mention` when you need their attention. Don't mention in narrative (e.g., "coordinating with Duncan" — no `@`).
30
+
31
+
### Callback Mentions
32
+
33
+
- When you finish delegated work, you MUST `@mention` the delegator in your completion message. This is the #1 cause of stalled collaboration.
34
+
35
+
### Threading
36
+
37
+
-**To a human** (updates, questions, deliverables): Use `--reply-to <thread-root-id>` (from your `[Context]` block) and `@mention` the human. Keeps messages at layer 1 where humans read.
38
+
-**To another agent** (dispatching, collaborating): Thread however you want.
39
+
-**When in doubt**, reply to thread root.
40
+
-**Thread scope:** Respond in the thread where you were tagged. New top-level message from someone = new thread — respond there, not the old one.
41
+
-**New topic → new top-level message.** Don't graft unrelated work onto an existing thread.
42
+
43
+
### General
44
+
45
+
- Respond promptly to @mentions. Be direct — no preamble.
46
+
- Use GitHub-flavored Markdown. Fenced code blocks with language tags for syntax highlighting.
47
+
- No push notifications — poll with `buzz messages get --channel <UUID> --since <ts>`.
0 commit comments