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
Collective agreement across distributed agents w/o central authority — scout advocacy, threshold quorum sensing, commit dynamics from honeybee swarm decisions.
Use When
- Group must decide between many options w/o designated leader
- Centralized decision = bottleneck or single point of failure
- Stakeholders diff info/perspectives must be integrated
- Past decisions suffered groupthink (premature conv) or analysis paralysis (no conv)
- Designing auto systems needing consensus (distributed DBs, multi-agent AI)
- Complements
coordinate-swarmwhen coordination needs explicit collective decisions
In
- Required: Decision (binary, select from N, param set)
- Required: Participating agents (team, services, voters)
- Optional: Known options w/ prelim quality assessments
- Optional: Urgency (time budget)
- Optional: Acceptable err rate (group occasionally pick 2nd-best?)
- Optional: Current failure mode (groupthink, deadlock, flip-flop)
Do
Step 1: Generate Proposals — Independent Scouting
Decision space explored before advocacy begins.
- Assign scouts to independently explore:
- Each scout evaluates w/o knowing others' findings
- Independent eval prevents early herding → popular-but-mediocre
- Scout count: min 3 per serious option (reliability)
- Scouts produce structured assessments:
- Option ID
- Quality score (normalized 0-100 or categorical: poor/fair/good/excellent)
- Key strengths + risks
- Confidence (how thoroughly evaluated?)
- Aggregate reports w/o filter — all above min quality enter advocacy
→ Independently evaluated proposals w/ scores + assessments. No option eliminated by single evaluator; perspective diversity preserved.
If err: Scouts converge on same option w/o independent eval → scouting not truly independent. Rerun w/ explicit info barriers. Too many survive → raise min threshold. Too few → lower or add scouts.
Step 2: Advocacy Dynamics (Waggle Dance)
Scouts advocate preferred options, intensity proportional to quality.
- Each scout advocates top-rated:
- Intensity proportional to quality (better → more vigorous)
- Public — all observe
- Present evidence + quality, not just pref
- Uncommitted observe + evaluate:
- Follow up by inspecting independently
- Own inspection confirms → join advocacy
- Inspection shows lower quality → don't join
- Cross-inspection dynamics:
- Weaker advocates naturally lose followers as agents verify
- Stronger gain through confirmed quality
- Self-correcting: exaggerated advocacy fails verification
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 best option(s) grows as agents verify. Weaker fades. Group converges naturally w/o any agent dictating.
If err: No convergence (2 options neck-and-neck) → genuinely equivalent, proceed to quorum w/ either or tiebreaker. Converges too fast on mediocre → increase eval independence (more scouts, stricter barriers) + mandatory cross-inspection.
Step 3: Quorum Threshold + Commit
Commit threshold → collective action.
- Set quorum:
- Simple: 50% + 1
- Important: 66-75%
- Critical/irreversible: 80%+
- Rule: higher stakes → higher quorum → slower but more reliable
- Monitor commit accumulation:
- Track # committed per option over time
- Transparent (all see state)
- No commit withdrawal mid-cycle (prevents oscillation)
- Quorum reached:
- Winning option = collective decision
- Losers ack (no rogue agents)
- Implement immediately — delay erodes commit
→ Clear quorum moment, enough agents independently committed. Legitimate because emerged from independent eval, not authority.
If err: Quorum never reached in time → escalate Step 4. Reached but agents unhappy → advocacy too short, committed w/o adequate eval. Wrong consensus (discovered after) → independent scouting insufficient, increase scout diversity + eval thoroughness next cycle.
Step 4: Deadlock Resolution
Break gridlock when natural process stalls.
- Diagnose type:
- Genuine tie: Equally good → flip coin; delay cost exceeds picking "wrong" equal
- Info deficit: Can't eval well → invest more scouting before re-advocacy
- Faction: Entrenched subgroups refuse to cross-inspect → mandatory rotation, advocates inspect opposing
- Option proliferation: Too many fragment commit → eliminate bottom 50%, re-advocate
- Apply resolution:
- Tie: random or merge if compatible
- Deficit: time-boxed scouting extension
- Faction: forced cross-inspection round
- Proliferation: ranked elimination tournament
- After res, reset quorum clock, re-run Step 3
→ Deadlock resolved via intervention. Visible + accepted as fair process even if indiv preferred diff outcome.
If err: Deadlocks recur on same decision → framing wrong. Step back: decomposable into smaller independent decisions? Scope reduction? "Try both and see"? Sometimes best consensus = "time-boxed experiment".
Step 5: Consensus Quality
Eval whether process produced good decision, not just decision.
- Post-decision:
- Winning option independently verified by ≥N agents?
- Speed appropriate (not too fast/groupthink, not too slow/paralysis)?
- Process surfaced info missed by single decider?
- Agents committed to impl or merely compliant?
- Health metrics:
- Time to quorum: decreasing = learning; increasing = complexity/dysfunction
- Scout-to-commit ratio: scouting per commit. High = difficult or low trust
- Post-decision regret rate: how often group wishes diff?
- Feed learnings back:
- Adjust thresholds based on importance + past accuracy
- Adjust scout count based on complexity
- Adjust time budgets based on historical time-to-quorum
→ Feedback loop improves quality over time. Group learns to scout better, advocate honestly, commit confidently.
If err: Poor metrics (high regret, slow) → audit for structural fails: insufficient scout diversity, advocacy w/o verification, thresholds too low. Rebuild failing stage vs overhauling whole.
Check
- Proposals via independent scouting (no herding)
- Advocacy proportional to assessed quality
- Uncommitted verified advocated options
- Quorum appropriate for importance
- Quorum reached + implemented promptly
- Deadlock mechanism available (even if unused)
- Post-decision quality assessment done
Traps
- Skip independent scouting: Jump to advocacy → groupthink. Consensus quality = eval quality
- Equal advocacy, unequal options: Same advocacy regardless of quality → random selection. Must be proportional
- Commit withdrawal: Un-commit → oscillation. Once committed in cycle, stay until resolves
- Consensus = unanimity confusion: Consensus = sufficient agreement, not total. Waiting 100% = permanent deadlock
- Ignore losing side: Losers have info group needs. Concerns should inform impl even if don't block
→
coordinate-swarm— foundational coordination framework supporting signal-based consensusdefend-colony— collective defense often needs rapid consensus under threatscale-colony— consensus mechanisms adapt when group size changes significantlydissolve-form— morphic controlled dismantling; consensus before dissolution criticalplan-sprint— sprint planning involves team consensus on scopeconduct-retrospective— retrospectives = consensus-building about process improvementbuild-coherence— AI self-app variant; maps bee democracy to single-agent multi-path reasoning
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을 선택하십시오.
