i18n/de/skills/build-consensus/SKILL.md
Achieve distributed agreement ohne central authority using bee democracy, threshold voting, and quorum sensing. Umfasst proposal generation, advocacy dynamics, commitment thresholds, deadlock resolution, and consensus quality assessment. Verwenden wenn a group must decide zwischen options ohne a designated leader, when centralized decision-making is a bottleneck, when stakeholders have different perspectives to integrate, or when designing automated systems that must reach consensus wie z.B. distributed databases or multi-agent AI.
npx skillsauth add pjt222/agent-almanac build-consensusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Achieve collective agreement across distributed agents ohne a central authority — using scout advocacy, threshold quorum sensing, and commitment dynamics modeled on honeybee swarm decision-making.
coordinate-swarm when the coordination requires explicit collective decisionsSicherstellen the decision space is adequately explored vor any advocacy begins.
Erwartet: A set of independently evaluated proposals with quality scores and assessments. No option wurde eliminated by a single evaluator; diversity of perspective is preserved.
Bei Fehler: If scouts converge on the same option ohne 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.
Erlauben scouts to advocate for their preferred options, with advocacy intensity proportional to quality.
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 │
└─────────────────────────────────────────────────────────┘
Erwartet: 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 ohne any agent dictating the choice.
Bei Fehler: If advocacy doesn't converge (two options remain neck-and-neck), the options kann 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.
Definieren the commitment threshold that triggers collective action.
Erwartet: 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.
Bei Fehler: If quorum is never reached innerhalb 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 ohne adequate evaluation. If the consensus was wrong (discovered nach the fact), the independent scouting was insufficient — increase scout diversity and evaluation thoroughness in the next cycle.
Break decision gridlock when the natural consensus process stalls.
Erwartet: Deadlock resolved durch the appropriate intervention. The resolution is visible and accepted by the group as fair process, even if individual agents preferred a different outcome.
Bei Fehler: If deadlocks recur on the same decision, the decision framing kann 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."
Bewerten whether the consensus process produced a good decision, not just a decision.
Erwartet: A feedback loop that improves consensus quality over time. The group learns to scout more effectively, advocate more honestly, and commit more confidently.
Bei Fehler: If consensus quality metrics are poor (high regret, slow decisions), audit der Prozess for structural failures: insufficient scouting diversity, advocacy ohne verification, or thresholds set too low for the decision type. Rebuild the specific failing stage anstatt overhauling the entire process.
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 erheblichdissolve-form — morphic skill for controlled dismantling, where consensus vor 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 resolutiontesting
Launch all available agents in parallel waves for open-ended hypothesis generation on problems where the correct domain is unknown. Use when facing a cross-domain problem with no clear starting point, when single-agent approaches have stalled, or when diverse perspectives are more valuable than deep expertise. Produces a ranked hypothesis set with convergence analysis and adversarial refinement.
tools
Write integration tests for a Node.js CLI application using the built-in node:test module. Covers the exec helper pattern, output assertions, filesystem state verification, cleanup hooks, JSON output parsing, error case testing, and state restoration after destructive tests. Use when adding tests to an existing CLI, testing a new command, verifying adapter behavior across frameworks, or setting up CI for a CLI tool.
development
Screen a proposed trademark for conflicts and distinctiveness before filing. Covers trademark database searches (TMview, WIPO Global Brand Database, USPTO TESS), distinctiveness analysis using the Abercrombie spectrum, likelihood of confusion assessment using DuPont factors and EUIPO relative grounds, common law rights evaluation, and goods/services overlap analysis. Produces a conflict report with a risk matrix. Use before adopting a new brand name, logo, or slogan — distinct from patent prior art search, which uses different databases, legal frameworks, and analysis methods.
tools
Scaffold a new CLI command using Commander.js with options, action handler, three output modes (human-readable, quiet, JSON), and optional ceremony variant. Covers command naming, option design, shared context patterns, error handling, and integration testing. Use when adding a command to an existing Commander.js CLI, designing a new CLI tool from scratch, or standardizing command structure across a multi-command CLI.