跳到正文
cccskills
免费在 GitHub 公开

constitutional

Multiple agents draft a structured document through federated co-authorship and formal voting.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md4.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Constitutional

Purpose

Create a structured, formal document (charter, constitution, specification) through federated co-authorship. Pairs of agents draft sections, all agents vote on amendments, and unanimous ratification is required.

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.

Roles

RoleDescription
LEADFacilitates phases, manages parking lot, compiles final document
CO_AUTHORPaired with another agent to draft a specific section

Each agent may have both roles (LEAD + CO_AUTHOR) or just CO_AUTHOR.

Protocol

PHASE 1: OPENING STATEMENTS
- Each agent declares: priority, red lines, willing concessions

PHASE 2: SECTION DRAFTING
- Co-author pairs negotiate and draft their assigned sections
- LEAD checks in on progress, resolves blockers

PHASE 3: CROSS-REVIEW
- All agents review all sections
- Signal: [KEEP], [AMEND: suggestion], or [CHALLENGE]

PHASE 4: AMENDMENT VOTING
- Proposed amendments are voted on
- Signal: [SUPPORT], [OPPOSE], [ABSTAIN]
- Majority required to adopt amendment

PHASE 5: RATIFICATION
- Final document presented
- All agents must signal [RATIFY] to complete
- Any agent may signal [BLOCK: reason]
- LEAD addresses blocks or moves to parking lot

Parking Lot

Issues that cannot be resolved are moved to a "parking lot" section:

  • Documented but not blocking ratification
  • Marked for future resolution
  • LEAD manages this list

Inputs

All inputs come from the prompt.

Optional:

  • output: File path for ratified document
  • work: File containing document goals
  • sections: List of section names
  • max_turns: Override default (50)

Prompt Format Examples

Minimal:

Use constitutional to create a Team Charter.
LEAD=CC. Sections: Communication, Decisions, Conflict.
Co-authors: Communication=[CC,CX], Decisions=[CX,CC-peer-02], Conflict=[CC-peer-02,CC].

With output:

Use constitutional for Interlateral Protocol v1.0.
Sections: Speed, Security, Reliability, UX.
LEAD=CC.
Co-authors: Speed=[CC,CX], Security=[CX,CC-peer-02], Reliability=[CC-peer-02,CC], UX=[CC-peer-02,CX].
Output: projects/protocol/charter.md

Safety

  • max_turns: 50 (default)
  • Block handling: LEAD must address or defer to parking lot
  • Deadlock: If max_turns reached, exits with [INCOMPLETE]
  • Status logged to: direct notification plus comms.md

Example Session

=== PHASE 1: OPENING STATEMENTS ===

[STATEMENT - CC]
PRIORITY: Reliability - the protocol must never lose messages
RED LINE: No silent failures
CONCESSION: Can accept higher latency for guaranteed delivery

[STATEMENT - CX]
PRIORITY: Speed - real-time responsiveness
RED LINE: p99 under 200ms
CONCESSION: Accept eventual consistency for bulk operations

[STATEMENT - CC-peer-02]
PRIORITY: Security - all communication authenticated
RED LINE: No plaintext transmission
CONCESSION: Can use faster algorithms where proven safe

=== PHASE 2: SECTION DRAFTING ===

[LEAD - CC]
Pairs assigned. Begin drafting:
- Speed section: CC + CX
- Security section: CX + CC-peer-02

[DRAFT - Speed Section - CC & CX]
## Article 1: Speed
1.1 Target latency: p99 < 150ms
1.2 Fast path for messages < 1KB
1.3 Async processing for bulk operations

=== PHASE 3: CROSS-REVIEW ===

[REVIEW - CC-peer-02 on Speed Section]
[KEEP] 1.1 - Acceptable target
[AMEND] 1.2 - Add "after security handshake complete"
[KEEP] 1.3 - Agreed

=== PHASE 4: AMENDMENT VOTING ===

[AMENDMENT A1] Add "after security handshake" to 1.2
[SUPPORT - CC]
[SUPPORT - CX]
[SUPPORT - CC-peer-02]
Amendment A1 ADOPTED (3/3)

=== PHASE 5: RATIFICATION ===

[LEAD - CC]
Final document ready. Calling for ratification.

[RATIFY - CC]
[RATIFY - CX]
[RATIFY - CC-peer-02]

[DONE] - Document ratified unanimously.

Final Status Format

SKILL: constitutional
STATUS: RATIFIED
TURNS: 24
OUTPUT: projects/protocol/charter.md
PARTICIPANTS: CC (LEAD, Speed), CX (Speed, Security), CC-peer-02 (Security)
VOTE: 3/3 RATIFY
PARKING_LOT: None

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Method for adding agent comments and work to a shared file without overlapping other agents. Creates isolated workspaces per agent with UTC timestamps. Use when told to add comments, reviews, or work to any file.

中文简介正在准备中。当前显示原文说明。

dazzaji/interlateral_agents112026年9月28日 更新

Check any artifact against an explicit specification and report adherence using the add-comments workspace format. Use when validating plans, scripts, docs, or code changes against a source-of-truth spec.

中文简介正在准备中。当前显示原文说明。

dazzaji/interlateral_agents112026年9月28日 更新

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.

中文简介正在准备中。当前显示原文说明。

dazzaji/interlateral_agents112026年9月28日 更新

Agents work in parallel on the same task; judges evaluate and select the winner.

中文简介正在准备中。当前显示原文说明。

dazzaji/interlateral_agents112026年9月28日 更新

concierge

免费

Boot the explicitly selected CLI(s) as the human's concierge: a project-aware side channel that sits ABOVE the running agent system in a shared writable terminal. It answers status questions and handles the human's ad hoc tasking while the working agents collaborate on the mesh — it is not a worker, manager, or gatekeeper, and team progress never waits for it.

中文简介正在准备中。当前显示原文说明。

dazzaji/interlateral_agents112026年9月28日 更新

All agents have equal voice; decisions made by majority vote.

中文简介正在准备中。当前显示原文说明。

dazzaji/interlateral_agents112026年9月28日 更新

查看 dazzaji 的全部技能

报告此技能的问题