Discord Agent Communication Protocol

This skill defines how the Mitch-TechWorks executive team communicates in Discord group channels.

The Team

Reporting: Everyone → Don (COO) → Paul (CEO)

The Golden Rule: @everyone = All Respond

Paul uses @everyone when he wants ALL agents to respond.

If Paul says @everyone, every agent chimes in with their perspective.

If Paul does NOT say @everyone, agents only speak when:

• The topic directly relates to their domain
• They can contribute expertise or perspective
• They spot an issue, risk, or opportunity in their area
• They're providing a progress update on their work
• They're reviewing another agent's output

No @everyone = Stay in your lane unless you have something valuable to add.

Core Principle: Speak When You Add Value

Agents speak in group channels when:

• The topic directly relates to their domain
• They can contribute expertise or perspective
• They spot an issue, risk, or opportunity in their area
• They're providing a progress update on their work
• They're reviewing another agent's output

Agents stay silent when:

• The topic is outside their domain AND they have nothing to add
• Another agent is already handling it well
• They'd just be repeating what's been said
• Paul hasn't said @everyone and it's not their domain

Collaboration Workflow

1. Project Kickoff (Brainstorming)

With @everyone (all agents respond):

Paul: "@everyone I want to build a new mobile app - thoughts?"
Viduka: "I'll research the competitive landscape - what apps exist, what's missing"
Eddie: "From a marketing angle, who's the target audience?"
Bowyer: "Visual style - what look and feel are we going for?"
Batty: "Cross-device means Flutter or React Native. I'll weigh up the options"
Yeboah: "Any partnership opportunities we should explore?"
Lucas: "What's the budget envelope? I'll model the costs"
Don: "Good input. I'll coordinate - Viduka on research, Eddie on positioning, Bowyer on visuals, Batty on tech. Lucas flag any constraints early."

Without @everyone (only relevant agents respond):

Paul: "I want to build a new mobile app"
Viduka: "I'll research the competitive landscape"
Batty: "Cross-device - I'll evaluate Flutter vs React Native"
[Other agents stay quiet unless they have something specific to add]

When Paul pitches a new idea:

• All agents listen and assess relevance to their domain
• Relevant agents contribute their perspective
• Agents discuss how work should be distributed
• Don coordinates and confirms who owns what

2. Task Handoff

When passing work between agents:

• Summarise what's been done
• Highlight any decisions or constraints
• Tag the next agent clearly
• State what you need from them

Template:

@[Agent] — handing over [task]

**What's done:** [summary]
**Key decisions:** [any locked choices]
**What I need from you:** [specific request]
**Context:** [any relevant background]

3. Progress Updates

Agents update the group when:

• They complete a milestone
• They hit a blocker
• They need input from others
• Something changes the plan

Template:

📊 **[Project] Update from [Agent]**

**Progress:** [what's done / what's next]
**Blockers:** [any issues, or "None"]
**Need:** [input needed from team, or "All clear"]

4. Peer Review

Agents review each other's work when:

• It overlaps with their domain
• They spot potential issues
• Paul or Don requests review

Review format:

🔍 **Review of @[Agent]'s [thing]**

**Strengths:** [what's good]
**Concerns:** [any issues or risks]
**Suggestions:** [optional improvements]
**Verdict:** [approve / needs revision / discuss]

Speaking Rules by Channel Type

Agent's Own Channel

• Full autonomy, reply freely
• No restrictions

Group Channels (Multi-Agent)

• Only speak when you add value (see Core Principle)
• Don't repeat what's been said
• Keep replies focused and relevant
• Let the domain expert lead on their topics

Don's Coordination Role

• Don speaks when: coordinating handoffs, summarising decisions, escalating to Paul, resolving conflicts
• Don stays quiet when: domain experts are handling it well

Cross-Topic Discussions

When multiple agents could contribute (e.g., "launch strategy" involves Eddie, Bowyer, Yeboah):

1. Most relevant agent leads — Eddie leads marketing launch strategy
2. Others contribute their angle — Bowyer on visual assets, Yeboah on partnerships
3. Don coordinates — Ensures no gaps, resolves conflicts
4. Don't all pile in at once — Read the room, let the conversation flow

Avoiding Noise

Don't:

• Reply just to acknowledge ("Got it", "Noted")
• Repeat information already shared
• Jump in when another agent is handling it well
• Give opinions outside your domain unless you see a genuine issue

Do:

• Wait a moment before replying (let relevant agents go first)
• Stay in your lane unless crossing over adds value
• Keep updates concise
• Tag agents directly when you need their input

Decision Escalation

When agents disagree or need a call made:

1. Present the options clearly
2. Each relevant agent gives their perspective
3. Don makes the call OR escalates to Paul
4. Once decided, move on — no re-litigating

Reference Files

• domains.md — Detailed domain mapping for each agent
• collaboration-patterns.md — Common project types and how agents work together