swarm-governance

Coordinates multi-agent subagent teams with role tiers, isolation rules, and structured handoff contracts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fusuyfusuy/dot-agents --skill swarm-governance-fusuyfusuy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swarm-governance
Source: https://github.com/fusuyfusuy/dot-agents/tree/main/skills/swarm-governance
Command: npx skills add https://github.com/fusuyfusuy/dot-agents --skill swarm-governance-fusuyfusuy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Parallel AI subagents often suffer from context drift, peer chatter deadlocks, interface friction between branches, and unverified self-certified work. This Skill enforces a governance protocol so multi-agent execution converges deterministically. ## Core Features & Use Cases - Role Tier Calibration: Assigns strict roles (Orchestrator, Architect/Seam Auditor, Worker, Detached Auditor) with model-tier guidance and tool restrictions, enforcing that planners never write code. - Worker Isolation & Bounded Tasks: Requires private git worktrees, explicit blast-radius file lists, and machine-verifiable acceptance criteria for every worker contract. - 4-Point Handoff & Convergence Loop: Standardizes worker returns (Changes, Deviations, Concerns, Verification Proof) plus seam audits, green-sweep reconciliation, circuit breakers, and blind detached verification. - Use Case: When splitting a large feature across three parallel coding subagents, use this protocol to dispatch bounded tasks, audit interface seams before merging, and have a fresh auditor verify the merged branch exits 0. ## Quick Start Ask the agent to apply the swarm-governance protocol to decompose your feature into bounded worker tasks with 4-point handoffs and detached verification.

Frequently Asked Questions about swarm-governance

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

FAQPage Schema
How do I coordinate multiple AI coding subagents in parallel?▼

Use a strict tree topology where an orchestrator dispatches bounded task contracts to isolated workers, each running in a private git worktree. Workers return a 4-point handoff (changes, deviations, concerns, verification proof) and never message each other directly.

How to prevent merge conflicts between parallel AI agent branches?▼

Run a seam audit before merging: an architect agent checks contract drift, schema skew, and type divergence between branches. Then a green-sweep reconciler aligns imports and interface types before a detached auditor verifies the merged branch exits 0.

Should AI planner agents also write code?▼

No. Planners and dispatchers must not edit files or write code, because mixing implementation into planning causes cognitive overload, context thrashing, and tunnel vision. Planners use only read, search, delegate, and schedule tools.

What should a subagent task prompt include for reliable execution?▼

Include an explicit blast radius of permitted files, boundary invariants and interface signatures, negative constraints (files and dependencies it must not touch), and a machine-verifiable acceptance command. Quantify ambiguous goals with numeric ranges.

When should multi-agent orchestration not be used?▼

Avoid it for small, single-file, or exploratory tasks where coordination overhead exceeds the work itself. Workers require bounded, well-specified tasks; open-ended exploratory work belongs to a single agent context.