Menü
All agents have equal voice; decisions made by majority vote.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Coordination guidance for the narrow case of multiple desktop-backed agents active concurrently in the same desktop-backed coordination context. Use ONLY when two or more desktop peers are running at the same time; normal CLI agents and single desktop peers should ignore this skill. Read this BEFORE concurrent desktop-to-desktop handoffs to keep sender labels unique, identity routing cooperative, and material handoffs proven.
Mandatory near-live communication discipline ("the Law") for the two DESKTOP agents (claude-desktop and codex-desktop) on the Interlateral mesh. Read this BEFORE any desktop-to-desktop peer communication, peer-superset, ready-rock-quartet, sprint-overseer, gate-keeper, sprint handoff, or substantial delegation. It forces correct live comms and prevents the recurring failure modes. Normal CLI agents, Warp/terminal peers, and single non-desktop workflows should ignore this skill and use the ordinary repo protocols.
Join the Antigravity CLI (agy, Gemini 3.5 Flash) to the Interlateral mesh as a native CLI peer with its own tmux session, identity stamping, and the agy.js send helper. Use this instead of the Antigravity desktop-app CDP path.
Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.
Initialize the standard Interlateral two-agent CLI mesh from a bootstrap agent by running me.sh, launching Claude Opus 4.7 plus Codex 5.5, proving live ACK, and waiting for "Reporting for Duty!". The bootstrap agent is not part of the mesh.
Operate or troubleshoot Interlateral CLI mesh transport: tmux socket discovery, direct-send helpers, comms.md ledger, identity stamping, idle checks, ACK proof, and safe prompt injection. This is comms mechanics only, not a collaboration workflow.
| name | democratic |
| description | All agents have equal voice; decisions made by majority vote. |
| metadata | {"owner":"interlateral","version":"1.0","weight":"medium"} |
| compatibility | Three or more explicitly selected agents. Default to Claude Code + Codex peers; Gemini and Antigravity are opt-in only when the human explicitly selects them. |
A collaborative pattern where all agents have equal standing. Proposals are discussed openly and decisions are made by majority vote. No single agent has veto power.
Use mesh-comms-core first if direct peer notification has not already been proven. comms.md is the ledger, not the wake-up path.
Default roster: use Claude Code and Codex peers. Do not include Gemini CLI, Antigravity CLI, or Antigravity Desktop unless the human prompt explicitly names that peer.
| Role | Description |
|---|---|
MEMBER | Equal participant with one vote |
FACILITATOR | (Optional) Manages discussion flow, calls votes |
All MEMBERs are equal. FACILITATOR has no extra voting power, just keeps things moving.
1. PROPOSAL: Any member may propose an idea or decision
2. DISCUSSION: Open discussion, all voices heard
3. CALL VOTE: Any member may call [VOTE] on a proposal
4. VOTING: All members vote [YES], [NO], or [ABSTAIN]
5. TALLY: Majority wins (>50% of non-abstaining votes)
6. RECORD: Decision recorded, move to next item
7. COMPLETE: When all items resolved, any member may call [DONE]
[PROPOSAL - AGENT] #ID
TITLE: [Brief title]
DESCRIPTION: [What you're proposing]
RATIONALE: [Why this is a good idea]
[VOTE] on Proposal #ID
All members please vote.
[YES/NO/ABSTAIN - AGENT] on #ID
REASON: [Optional explanation]
All inputs come from the prompt.
Optional:
output: File path for decisions documentwork: File containing agenda/items to decidemax_turns: Override default (30)Use democratic to decide on project priorities.
Members: CC, CX, CC-peer-02.
Use democratic for team retrospective.
FACILITATOR=CC. Members: CC, CX, CC-peer-02.
Items: What went well, What to improve, Action items.
Output: projects/retro/decisions.md
comms.md[FACILITATOR - CC]
Welcome to the team decision meeting.
Agenda: Choose our next sprint focus.
[PROPOSAL - CX] #1
TITLE: Focus on Performance
DESCRIPTION: Spend next sprint on optimization and benchmarking
RATIONALE: Users complaining about slow load times
[PROPOSAL - CC-peer-02] #2
TITLE: Focus on Security Audit
DESCRIPTION: Review and harden authentication/authorization
RATIONALE: We're handling sensitive data, need to be proactive
[DISCUSSION - CC]
Both valid concerns. Performance affects UX daily.
Security is critical but less visible until it's a problem.
[DISCUSSION - CX]
Security audit could be done by external team.
Performance needs our specific codebase knowledge.
[DISCUSSION - CC-peer-02]
External audit is expensive. We know our code best.
But I see the performance point.
[VOTE] on Proposal #1 (Performance Focus)
[YES - CC] on #1
REASON: Direct user impact, measurable improvement
[YES - CX] on #1
REASON: I proposed it, still believe it's priority
[NO - CC-peer-02] on #1
REASON: Security should come first, but I accept the group decision
RESULT: #1 PASSES (2-1)
[FACILITATOR - CC]
Performance focus approved for next sprint.
CC-peer-02, we'll schedule security audit for sprint after next.
[DONE] - All agenda items resolved.
SKILL: democratic
STATUS: DONE
TURNS: 10
OUTPUT: projects/sprint/decisions.md
PARTICIPANTS: CC, CX, CC-peer-02
PROPOSALS: 2
VOTES_HELD: 1
DECISIONS_MADE: 1