message-bus

Manage inter-agent communication through a file-based message queue and board deliberation protocol.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill message-bus-geargrindadmin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: message-bus
Source: https://github.com/Geargrindadmin/gg-agentic-harness/tree/main/.agent/skills/message-bus
Command: npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill message-bus-geargrindadmin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a robust, file-based message queue for seamless communication and coordination between different agents (workers and board directors) within the system, enabling parallel execution and complex decision-making processes.

Core Features & Use Cases

  • Progress Updates: Workers can report their task progress.
  • Task Signaling: Agents can signal task completion or failure.
  • File Locking: Prevents race conditions by managing access to shared files.
  • Board Deliberation: Facilitates structured discussions and voting among directors for critical decisions.
  • Use Case: A worker agent needs to process a file. It acquires a lock on the file, reports its progress, and upon completion, signals the orchestrator and other interested agents via the message bus.

Quick Start

Initialize the message bus for the 'feature-xyz_20260201' track.

Frequently Asked Questions about message-bus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate parallel agent workflows without race conditions?

You can coordinate parallel agents using a file-based message queue that provides file locking to prevent race conditions. Workers report progress and signal task completion through the structured bus, enabling synchronized inter-agent communication.

How does a file-based message queue handle inter-agent communication?

Inter-agent communication is handled by allowing worker agents to send progress updates and task completion signals to an orchestrator. The queue uses file locking to manage shared file access and prevent concurrent write conflicts during execution.

What is board deliberation protocol for multi-phase agent decision-making?

Board deliberation protocol is a structured communication mechanism that facilitates discussions and voting among director agents for critical decisions. It enables multi-phase decision-making processes within coordinated agent workflows.

Can I use this message bus to signal task completion between worker agents?

Yes, the message bus supports task completion signaling between worker agents. Workers report their progress and upon completion, signal the orchestrator and other interested agents via the file-based message queue.

Does this message queue require external dependencies for file locking?

No external dependencies are required. The message bus operates independently using scripts to manage shared file access and coordinate inter-agent communication without relying on external libraries.

What are the limitations of a file-based message queue for agent coordination?

A file-based message queue relies on file locking, which may face throughput constraints under high concurrency compared to memory-based alternatives. It is designed for structured agent workflows and board deliberation rather than high-volume real-time messaging.