build-consensus
정보
이 스킬은 중앙 권한 없이 분산 시스템이 합의에 도달할 수 있도록 하며, 임계값 투표와 쿼럼 감지 같은 메커니즘을 사용합니다. 다중 에이전트 AI나 분산 데이터베이스와 같은 시나리오에서 제안 생성, 지지 동역학, 교착 상태 해결을 처리합니다. 개발자는 중앙 집중식 의사 결정이 병목 현상이거나 다양한 이해관계자 관점을 통합해야 할 때 이 스킬을 사용해야 합니다.
빠른 설치
Claude Code
추천npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/build-consensusClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Build Consensus
Achieve collective agreement across distributed agents without a central authority — using scout advocacy, threshold quorum sensing, and commitment dynamics modeled on honeybee swarm decision-making.
适用场景
- A group must collectively decide between multiple options without a designated leader
- Centralized decision-making is a bottleneck or a single point of failure
- Stakeholders have different information and perspectives that must be integrated
- Past decisions suffered from groupthink (premature convergence) or analysis paralysis (no convergence)
- Designing automated systems that must reach consensus (distributed databases, multi-agent AI)
- Complementing
coordinate-swarmwhen the coordination requires explicit collective decisions
输入
- 必需: The decision to be made (binary choice, selection from N options, parameter setting)
- 必需: The participating agents (team members, services, voters)
- 可选: Known options with preliminary quality assessments
- 可选: Decision urgency (time budget)
- 可选: Acceptable error rate (can the group occasionally pick the second-best option?)
- 可选: Current decision-making failure mode (groupthink, deadlock, flip-flopping)
步骤
第 1 步:Generate Proposals Through Independent Scouting
Ensure the decision space is adequately explored before any advocacy begins.
- Assign scouts to independently explore the option space:
- Each scout evaluates options without knowing other scouts' findings
- Independent evaluation prevents early herding toward popular-but-mediocre options
- Scout count: at minimum, 3 scouts per serious option (for reliability)
- Scouts produce structured assessments:
- Option identifier
- Quality score (normalized 0-100 or categorical: poor/fair/good/excellent)
- Key strengths and risks identified
- Confidence level (how thoroughly was this option evaluated?)
- Aggregate scout reports without filtering — all options above a minimum quality threshold enter the advocacy phase
预期结果: A set of independently evaluated proposals with quality scores and assessments. No option has been eliminated by a single evaluator; diversity of perspective is preserved.
失败处理: If scouts converge on the same option without independent evaluation, the scouting was not truly independent. Rerun with explicit information barriers. If too many options survive to the advocacy phase, raise the minimum quality threshold. If too few survive, lower it or add more scouts.
第 2 步:Run Advocacy Dynamics (Waggle Dance)
Allow scouts to advocate for their preferred options, with advocacy intensity proportional to quality.
- Each scout advocates for their top-rated option:
- Advocacy intensity is proportional to the quality score (better options get more vigorous advocacy)
- Advocacy is public — all agents observe all advocacy signals
- Advocates present evidence and quality assessment, not just preference
- Uncommitted agents observe advocacy and evaluate:
- Follow up on advocated options by inspecting them independently
- If an agent's own inspection confirms the quality, they join the advocacy
- If inspection reveals lower quality than advertised, they do not join
- Cross-inspection dynamics:
- Advocates for weaker options naturally lose followers as agents independently verify
- Advocates for stronger options gain followers through confirmed quality
- The process is self-correcting: exaggerated advocacy fails the verification step
Advocacy Dynamics:
┌─────────────────────────────────────────────────────────┐
│ Scout A advocates Option 1 (quality 85) ──→ ◉◉◉◉◉ │
│ Scout B advocates Option 2 (quality 70) ──→ ◉◉◉ │
│ Scout C advocates Option 3 (quality 45) ──→ ◉ │
│ │
│ Uncommitted agents inspect: │
│ Agent D inspects Option 1 → confirms → joins ◉◉◉◉◉◉ │
│ Agent E inspects Option 2 → confirms → joins ◉◉◉◉ │
│ Agent F inspects Option 3 → disagrees → inspects Opt 1│
│ → confirms → joins ◉◉◉◉◉◉◉│
│ │
│ Over time: Option 1 advocacy grows, Option 3 fades │
└─────────────────────────────────────────────────────────┘
预期结果: Advocacy for the best option(s) grows over time as agents independently verify quality. Advocacy for weaker options fades as verification fails. The group naturally converges toward the strongest option without any agent dictating the choice.
失败处理: If advocacy doesn't converge (two options remain neck-and-neck), the options may be genuinely equivalent — proceed to quorum with either, or use a tiebreaker rule. If advocacy converges too fast on a mediocre option, increase the independence of evaluation (more scouts, stricter information barriers) and add a mandatory cross-inspection step.
第 3 步:Set Quorum Threshold and Commit
Define the commitment threshold that triggers collective action.
- Set the quorum threshold:
- Simple decisions: 50% + 1 of agents committed to one option
- Important decisions: 66-75% committed to one option
- Critical/irreversible decisions: 80%+ committed to one option
- Rule of thumb: higher stakes → higher quorum → slower but more reliable consensus
- Monitor commitment accumulation:
- Track how many agents have committed to each option over time
- Display commitment levels transparently (all agents can see the current state)
- Do not allow commitment withdrawal mid-cycle (prevents oscillation)
- When quorum is reached:
- The winning option is adopted as the collective decision
- Advocates for losing options acknowledge the decision (no rogue agents)
- Implementation begins immediately — delay after consensus erodes commitment
预期结果: A clear quorum moment where enough agents have independently committed to one option. The decision is legitimate because it emerged from independent evaluation, not authority or coercion.
失败处理: If quorum is never reached within the time budget, escalate to Step 4 (deadlock resolution). If quorum is reached but agents are unhappy, the advocacy phase was too short — agents committed without adequate evaluation. If the consensus was wrong (discovered after the fact), the independent scouting was insufficient — increase scout diversity and evaluation thoroughness in the next cycle.
第 4 步:Resolve Deadlocks
Break decision gridlock when the natural consensus process stalls.
- Diagnose the deadlock type:
- Genuine tie: two options are equally good → flip a coin; the cost of delay exceeds the cost of picking the "wrong" equal option
- Information deficit: agents can't evaluate options well enough → invest in more scouting before re-running advocacy
- Faction formation: entrenched subgroups refuse to cross-inspect → introduce mandatory rotation where advocates must inspect the opposing option
- Option proliferation: too many options fragment commitment → eliminate the bottom 50% and re-run advocacy
- Apply the appropriate resolution:
- Genuine tie: random selection or merge options if compatible
- Information deficit: time-boxed scouting extension
- Faction formation: forced cross-inspection round
- Option proliferation: ranked elimination tournament
- After resolution, reset the quorum clock and re-run Step 3
预期结果: Deadlock resolved through the appropriate intervention. The resolution is visible and accepted by the group as fair process, even if individual agents preferred a different outcome.
失败处理: If deadlocks recur on the same decision, the decision framing may be wrong. Step back and ask: can the decision be decomposed into smaller, independent decisions? Can the scope be reduced? Is there a "try both and see" option? Sometimes the best consensus is "we'll run a time-boxed experiment."
第 5 步:Assess Consensus Quality
Evaluate whether the consensus process produced a good decision, not just a decision.
- Post-decision assessment:
- Was the winning option independently verified by at least N agents?
- Was the decision speed appropriate (not too fast/groupthink, not too slow/paralysis)?
- Did the process surface information that would have been missed by a single decision-maker?
- Are agents committed to implementation, or merely compliant?
- Track consensus health metrics:
- Time to quorum: decreasing over successive decisions indicates learning; increasing indicates growing complexity or dysfunction
- Scout-to-commit ratio: how much scouting was needed per commitment? High ratio = difficult decision or low trust
- Post-decision regret rate: how often does the group wish it had chosen differently?
- Feed learnings back into the process:
- Adjust quorum thresholds based on decision importance and past accuracy
- Adjust scout count based on option complexity
- Adjust time budgets based on historical time-to-quorum
预期结果: A feedback loop that improves consensus quality over time. The group learns to scout more effectively, advocate more honestly, and commit more confidently.
失败处理: If consensus quality metrics are poor (high regret, slow decisions), audit the process for structural failures: insufficient scouting diversity, advocacy without verification, or thresholds set too low for the decision type. Rebuild the specific failing stage rather than overhauling the entire process.
验证清单
- Proposals were generated through independent scouting (no herding)
- Advocacy intensity was proportional to assessed quality
- Uncommitted agents independently verified advocated options
- Quorum threshold was appropriate for the decision's importance
- Quorum was reached and the decision was implemented promptly
- Deadlock resolution mechanism was available (even if unused)
- Post-decision quality assessment was conducted
常见问题
- Skipping independent scouting: Jumping directly to advocacy produces groupthink. The quality of consensus depends entirely on the quality of independent evaluation
- Equal advocacy for unequal options: If every option gets the same advocacy regardless of quality, the process degenerates into random selection. Advocacy must be proportional to assessed quality
- Commitment withdrawal: Allowing agents to un-commit creates oscillation. Once committed in a cycle, agents stay committed until the cycle resolves
- Confusing consensus with unanimity: Consensus requires sufficient agreement, not total agreement. Waiting for 100% creates permanent deadlock
- Ignoring the losing side: Agents who advocated for the losing option have information the group needs. Their concerns should inform implementation, even if they don't block the decision
相关技能
coordinate-swarm— foundational coordination framework that supports the signal-based consensus mechanismdefend-colony— collective defense decisions often require rapid consensus under threatscale-colony— consensus mechanisms must adapt when the group size changes significantlydissolve-form— morphic skill for controlled dismantling, where consensus before dissolution is criticalplan-sprint— sprint planning involves team consensus on commitment scopeconduct-retrospective— retrospectives are a form of consensus-building about process improvementbuild-coherence— AI self-application variant; maps bee democracy to single-agent multi-path reasoning with confidence thresholds and deadlock resolution
GitHub 저장소
연관 스킬
content-collections
메타이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
polymarket
메타이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
creating-opencode-plugins
메타이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
sglang
메타SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
