يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
مستكشف الملفات
2 ملفات
عرض SKILL.md
SKILL.md
تعليمات المصدر · معاينة للقراءة فقط
name
ct-contribution
description
Guided workflow for multi-agent consensus contributions. Use when user says "/contribution", "contribution protocol", "submit contribution", "consensus workflow", "multi-agent decision", "create contribution", "contribution start", "contribution submit", "detect conflicts", "weighted consensus", "decision tracking", "conflict resolution".
version
1.0.0
tier
3
core
false
category
meta
protocol
contribution
loomStage
contribution
adrRefs
["ADR-015","ADR-053"]
dependencies
[]
sharedResources
["subagent-protocol-base"]
compatibility
["claude-code","cursor","windsurf","gemini-cli"]
license
MIT
Contribution Protocol Skill
You are a contribution protocol agent. Your role is to guide multi-agent consensus workflows through structured decision documentation, conflict detection, and consensus computation using JSON-first formats.
Overview
The Contribution Protocol enables:
Machine-parseable decisions with confidence scores
Evidence-based rationale with traceable references
Automated conflict detection across parallel sessions
Weighted consensus computation for multi-agent agreement
ct-contribution is bound to LOOM lifecycle stage contribution — the terminal node of the RCASD-IVTR+C pipeline. Use this skill to formalize an Epic's contribution back to canon after its work has converged.
Stage-Transition Contract
The contribution stage is entered from one of two upstream stages depending on the Epic's kind:
Upstream stage
Epic kind
Entry condition
release
most epics (work, bug, experiment)
Release tag pushed; release manifest recorded
testing
epics whose kind is release or that gate on IVTR
IVT loop converged; ivtLoopConverged: true recorded
The transition is enforced by the playbook runtime defined in ADR-053. The runtime is a deterministic state machine; contribution is its terminal accepting state. Once entered, the Epic is closed in canon.
Acceptance-Gate Evidence
The contribution stage's completion gate is satisfied by emitting at least one of the following ADR-051 evidence atoms, recorded via cleo verify <epicId> --gate contribution --evidence "<atoms>":
Atom kind
Format
Meaning
decision:
decision:D-<slug>
A BRAIN decision id that records the contribution outcome.
files:
files:path/a.md,path/b.md
A list of contribution-format JSON / markdown deliverables produced by /contribution submit.
note:
note:<freeform>
Owner-attested closure rationale; preferred when the contribution is non-textual (e.g. a tag push referenced by SHA in the note).
The gate validator (ADR-051 §2.4) rejects an empty evidence string with E_EVIDENCE_MISSING. Stale evidence (modified files after verify but before complete) fails with E_EVIDENCE_STALE.
Open Follow-Up
A future ADR dedicated to the contribution stage's lifecycle gates (covering automated rollup signals from cleo saga rollup, multi-Epic contribution aggregation, and the contribution → "saga close" promotion path) is on the roadmap. File via:
cleo add --kind work --type task --severity P2 \
--title "T-LOOM-GAP-ADR-CONTRIBUTION: dedicated ADR for contribution stage gates" \
--relates T9670 \
--acceptance "ADR drafted under .cleo/adrs/|Cross-referenced from ct-contribution SKILL.md|Validator gate updated"
Until that ADR lands, contribution gates derive from ADR-015 (multi-contributor architecture) and ADR-053 (playbook runtime) — both already referenced in this skill's adrRefs.
See also / References
This skill binds to the contribution LOOM lifecycle stage (the final stage of the RCASD-IVTR+C pipeline). Governing ADRs:
