Multi Agent Consensus
Install this marketplace plugin when you want three Claude subagents to vote unanimously before any phase handoff, with persisted evidence instead of a single model rubber-stamping its own work.
Overview
Multi-agent-consensus is a plugin marketplace for the Ship phase that runs three-agent unanimous validation with hard phase gates and persisted evidence in Claude Code.
What is this marketplace?
- Maps Lead, Alpha, and Bravo roles to Claude Code subagents with a unanimous voting rule
- Enforces hard gates at phase transitions so work cannot advance without full agreement
- Persists evidence per phase and role for auditability
- Targets validation and quality-assurance workflows in multi-agent pipelines
- MIT-licensed plugin v0.2.0 installable from a marketplace-of-one repo
- Marketplace bundles 1 plugin (multi-agent-consensus v0.2.0)
- Designed for 3-agent unanimous consensus
- MIT license
Community signal: 1 GitHub stars.
What problem does it solve?
A solo builder’s multi-agent pipeline can advance on one model’s optimistic self-review with no recorded dissent or proof at handoffs.
Who is it for?
Claude Code users running phased agent workflows who want mandatory unanimous review before moving from build work to ship-ready output.
Skip if: Builders who want fast single-agent codegen without governance overhead or formal voting rituals.
What do I get? / Deliverables
Phase transitions stay blocked until Lead, Alpha, and Bravo unanimously agree, with evidence retained per phase and role for the next step in the pipeline.
- Installed multi-agent-consensus plugin for Claude Code
- Unanimous gate behavior across Lead, Alpha, and Bravo roles
- Per-phase, per-role evidence records at transitions
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Canonical shelf is Ship because the plugin’s core value is quality gates and consensus review at phase transitions, not greenfield coding. Review subphase matches unanimous validation, Lead/Alpha/Bravo roles, and hard gates before the pipeline advances.
How it compares
Multi-agent governance plugin, not a generic coding skill or MCP server integration.
Common Questions / FAQ
Who is Multi Agent Consensus for?
Indie and solo builders using Claude Code subagents who need unanimous quality gates at pipeline phase changes.
When should I use Multi Agent Consensus?
Use it at phase transitions—after implementation chunks, before release review, or when evidence must be recorded before the workflow advances.
How do I add Multi Agent Consensus to my agent?
Run `claude plugin marketplace add krzemienski/Multi Agent Consensus`, then `claude plugin install Multi Agent Consensus@Multi Agent Consensus`, and wire the plugin into your phase-gate skill invocations.