hive-mind-advanced

Coordinate queen-led multi-agent collaboration with consensus and persistent memory.

2|1|Updated Jul 24, 2025
One-click install
npx skills add https://github.com/breddin/claude-flow-baseline --skill hive-mind-advanced-breddin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hive-mind-advanced
Source: https://github.com/breddin/claude-flow-baseline/tree/main/.claude/skills/hive-mind-advanced
Command: npx skills add https://github.com/breddin/claude-flow-baseline --skill hive-mind-advanced-breddin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? This Skill automates complex multi-agent coordination, decision-making, and knowledge sharing, enabling sophisticated collective intelligence systems for queen-led architectures. It streamlines the orchestration of specialized AI agents, ensuring robust consensus and persistent memory across tasks.

Core Features & Use Cases

  • Queen-Led Coordination: Direct specialized worker agents through a hierarchical architecture for strategic and tactical execution.
  • Byzantine Consensus: Ensure robust, fault-tolerant decision-making even with faulty agents, requiring a 2/3 majority for approval.
  • Collective Memory System: Share knowledge, context, and results across all agents for continuous learning and optimized retrieval.
  • Use Case: Orchestrate a full-stack development project where a queen agent directs coders, testers, and architects, ensuring all decisions are validated through consensus and knowledge is persistently shared across the team.

Quick Start

Basic initialization of the Hive Mind system

npx claude-flow hive-mind init

Spawn a swarm to build a microservices architecture

npx claude-flow hive-mind spawn "Build microservices architecture"

Frequently Asked Questions about hive-mind-advanced

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

FAQPage Schema
How do I coordinate multiple AI agents to work together on a project?

Multi-agent coordination uses a queen-led architecture where one agent directs specialized workers through hierarchical roles. This Skill orchestrates agent collaboration, consensus decision-making, and shared memory so all agents stay aligned on project goals and share knowledge continuously.

What is Byzantine consensus and why would I use it for agent decision-making?

Byzantine consensus is a fault-tolerant voting mechanism requiring a 2/3 majority approval, designed to handle faulty or unreliable agents. It ensures robust decisions even when some agents fail or behave unexpectedly, critical for mission-critical multi-agent systems.

How do I set up persistent memory across multiple agents?

Collective memory uses SQLite WAL persistence with LRU eviction to store and retrieve shared knowledge across all agents. This enables continuous learning—agents access prior decisions and context, avoiding redundant work and improving decision quality over time.

Can I use queen-worker orchestration for full-stack development projects?

Yes. A queen agent directs specialized workers (coders, testers, architects) through hierarchical roles while consensus validates major decisions and collective memory tracks all project context. This supports large-scale, ongoing projects requiring coordination across research, development, QA, and analytics.

What are the main consensus algorithms available for agent voting?

Three consensus algorithms are supported: Majority (simple vote), Weighted (votes with influence scores), and Byzantine (fault-tolerant 2/3 majority). Choose based on your fault tolerance needs and whether agents have different expertise levels.

Do I need specialized infrastructure to run a multi-agent swarm?

No specialized infrastructure is required. Session-based management and SQLite persistence work in standard environments. The Skill handles queen-worker role assignment, memory eviction, and consensus logic internally—start with the init command and spawn agents as needed.