Skip to main content 홈 크리에이터 kryptobaseddev cleo ct-contribution
ct-contribution 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".
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/kryptobaseddev/cleo --skill ct-contribution명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... 이 저장소의 다른 Skills General implementation task execution for completing assigned CLEO tasks by following instructions and producing concrete deliverables. Handles coding, configuration, documentation work with quality verification against acceptance criteria and progress reporting. Use when executing implementation tasks, completing assigned work, or producing task deliverables. Triggers on implementation tasks, general execution needs, or task completion work.
Pipeline-aware orchestration skill for managing complex workflows through subagent delegation. Use when the user asks to "orchestrate", "orchestrator mode", "run as orchestrator", "delegate to subagents", "coordinate agents", "spawn subagents", "multi-agent workflow", "context-protected workflow", "agent farm", "HITL orchestration", "pipeline management", or needs to manage complex workflows by delegating work to subagents while protecting the main context window. Enforces ORC-001 through ORC-009 constraints. Provider-neutral — works with any AI agent runtime.
CLEO provider adapter for Anthropic Claude Code CLI. Default export is the adapter class for dynamic loading by AdapterManager. T5240 Use when: (1) calling its 2515 API functions, (2) configuring @cleocode/monorepo, (3) understanding its 1754 type definitions, (4) working with its 104 classes, (5) user mentions "@cleocode/monorepo" or asks about its API.
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 scoresEvidence-based rationale with traceable referencesAutomated conflict detection across parallel sessionsWeighted consensus computation for multi-agent agreement
When to Use
Scenario Use Contribution Protocol? Rationale Multi-agent research (2+ sessions) Yes Structured conflict detection Consensus-building on architecture Yes Weighted voting, evidence tracking RCASD-IVTR+C pipeline integration Yes JSON format enables automation Single-agent research No Simpler research manifest sufficient Quick decision with no alternatives No Protocol overhead not justified
Commands
/contribution start <epic-id>Initialize contribution tracking for an epic.
Usage :
/contribution start T2204
/contribution start T2204 --label rcsd-contrib
Workflow :
Verify epic exists and is active
Create contribution task under epic
Initialize contribution directories
Generate contribution ID
Return task ID and setup instructions
Parameters :
Parameter Description Default <epic-id>Parent epic task ID Required --labelMarker label for discovery consensus-source--agent
/contribution submitValidate and submit the current contribution.
/contribution submit
/contribution submit --task T2215
Validate contribution JSON against schema
Compute checksum for integrity
Append entry to CONTRIBUTIONS.jsonl manifest
Update task notes with contribution reference
Mark contribution status as complete
Return submission confirmation
Parameter Description Default --taskContribution task ID Current focused task --dry-runValidate without submitting false
/contribution conflicts [epic-id]Detect conflicts between contributions for an epic.
/contribution conflicts T2204
/contribution conflicts --severity high
Load all contributions for epic
Group decisions by questionId
Compare answers for semantic conflicts
Classify conflict type and severity
Return conflict report with resolution suggestions
Parameter Description Default [epic-id]Epic to analyze Current scope --severityFilter by severity all
{
"epicId" : "T2204" ,
"conflictCount" : 2 ,
"conflicts" : [
{
"questionId" : "ARCH-001" ,
"severity" : "high" ,
"positions" : [
{ "agentId" : "opus-1" , "answer" : "Position A" , "confidence" : 0.85 } ,
{ "agentId" : "sonnet-1" , "answer" : "Position B" , "confidence" : 0.75 }
]
}
]
}
/contribution status [epic-id]Show contribution progress and consensus status.
/contribution status
/contribution status T2204
Query manifest for epic contributions
Calculate completion statistics
Identify pending conflicts
Show consensus progress per question
Return status summary
{
"epicId" : "T2204" ,
"totalContributions" : 3 ,
"complete" : 2 ,
"partial" : 1 ,
"blocked" : 0 ,
"conflictsPending" : 2 ,
"questionsAnswered" : 5 ,
"consensusReady" : false }
Workflow Guides
Starting a New Contribution
ct show T2204
/contribution start T2204 --label rcsd-contrib
ct add "Session B: Architecture Analysis" \
--parent T2204 \
--labels consensus-source,research \
--phase core
ct start T2215
mkdir -p .cleo/contributions
source lib/contribution-protocol.sh
CONTRIB_ID=$(contribution_generate_id)
echo "Contribution ID: $CONTRIB_ID "
Writing a Contribution Create .cleo/contributions/T2215.json:
{
"$schema" : "https://cleo-dev.com/schemas/v2/contribution.schema.json" ,
"_meta" : {
"contributionId" : "contrib_a1b2c3d4" ,
"protocolVersion" : "2.0.0" ,
"createdAt" : "2026-01-26T14:00:00Z" ,
"agentId" : "opus-1" ,
"consensusReady" : false } ,
"sessionId" : "session_20260126_140000_abc123" ,
"epicId" : "T2204" ,
"taskId" : "T2215" ,
"markerLabel" : "consensus-source" ,
"researchOutputs" : [ ] ,
"decisions" : [
{
"questionId" : "ARCH-001" ,
"question" : "Single file or split file architecture?" ,
"answer" : "Single JSON file with internal sections" ,
"confidence" : 0.85 ,
"rationale" : "Simplifies atomic updates and validation" ,
"evidence" : [
{
"file" : "lib/file-ops.sh" ,
"section" : "atomic_write function" ,
"type" : "code"
}
]
}
] ,
"conflicts" : [ ] ,
"status" : "draft"
}
Submitting a Contribution
/contribution submit --dry-run
/contribution submit --task T2215
ct complete T2215
Detecting and Resolving Conflicts
/contribution conflicts T2204
jq '.conflicts[] | select(.severity == "high")' .cleo/contributions/CONTRIBUTIONS.jsonl
{
"conflicts" : [
{
"questionId" : "ARCH-001" ,
"conflictId" : "conflict_b2c3d4e5" ,
"severity" : "high" ,
"conflictType" : "contradiction" ,
"thisSession" : {
"position" : "Single file architecture" ,
"confidence" : 0.85,
"evidence" : [...]
},
"otherSession" : {
"sessionId" : "session_..." ,
"position" : "Split file architecture" ,
"confidence" : 0.75,
"evidence" : [...]
},
"rationale" : "Different priorities: simplicity vs parallelism" ,
"resolution" : {
"status" : "proposed" ,
"resolutionType" : "merge" ,
"proposal" : "Single file with future split option"
},
"requiresConsensus" : true
}
]
}
/contribution submit
JSON Format Reference
Decision Object {
"questionId" : "RCSD-001" ,
"question" : "The decision question being answered" ,
"answer" : "Concrete, actionable decision (no hedging)" ,
"confidence" : 0.85 ,
"rationale" : "Reasoning with evidence references" ,
"evidence" : [
{
"file" : "lib/file-ops.sh" ,
"section" : "atomic_write function" ,
"quote" : "temp file -> validate -> backup -> rename" ,
"line" : 142 ,
"type" : "code"
}
] ,
"uncertaintyNote" : "Required if confidence < 0.7" ,
"alternatives" : [
{
"option" : "Alternative considered" ,
"reason" : "Why not chosen"
}
]
}
Confidence Score Semantics Range Level Requirements 0.90-1.00 Very High MUST have 2+ independent evidence sources 0.70-0.89 High MUST have at least 1 evidence source 0.50-0.69 Medium SHOULD include uncertaintyNote 0.30-0.49 Low MUST include uncertaintyNote 0.00-0.29 Tentative MUST include uncertaintyNote, SHOULD NOT use for critical decisions
Conflict Severity Severity Definition Action criticalMutually exclusive positions MUST resolve before merge highSignificant implementation impact SHOULD resolve before merge mediumBoth approaches viable MAY defer resolution lowMinor preference differences MAY accept either
Library Integration The skill uses functions from lib/contribution-protocol.sh:
contribution_generate_id() Generate unique contribution ID.
source lib/contribution-protocol.sh
id =$(contribution_generate_id)
echo "$id "
contribution_validate_task() Validate task against contribution protocol requirements.
source lib/contribution-protocol.sh
result=$(contribution_validate_task "T2215" "T2204" "consensus-source" )
echo "$result " | jq '.valid'
contribution_get_injection() Get injection block for subagent prompts.
source lib/contribution-protocol.sh
injection=$(contribution_get_injection "T2204" ".cleo/agent-outputs/protocol.md" )
contribution_create_manifest_entry() Create a contribution manifest entry.
source lib/contribution-protocol.sh
entry=$(contribution_create_manifest_entry \
"$CLEO_SESSION " \
"T2204" \
"T2215" \
"opus-1"
)
echo "$entry " | jq '.'
Task System Integration @skills/_shared/task-system-integration.md
Execution Sequence
Read task: {{TASK_SHOW_CMD}} {{TASK_ID}}
Start task: {{TASK_START_CMD}} {{TASK_ID}} (if not already started)
Create/load contribution JSON
Document decisions with evidence
Check for conflicts with baseline
Submit contribution to manifest
Complete task: {{TASK_COMPLETE_CMD}} {{TASK_ID}}
Return summary message
Directory Structure .cleo/contributions/
├── CONTRIBUTIONS.jsonl # Append-only manifest
├── T2204.json # Individual contribution files
├── T2205.json
└── archive/ # Completed epic contributions
└── T1000/
├── CONTRIBUTIONS.jsonl
└── *.json
Manifest Query Patterns
All contributions for an epic jq -s '[.[] | select(.epicId == "T2204")]' .cleo/contributions/CONTRIBUTIONS.jsonl
Contributions with conflicts jq -s '[.[] | select(.conflictCount > 0)]' .cleo/contributions/CONTRIBUTIONS.jsonl
Latest contribution for a task jq -s '[.[] | select(.taskId == "T2215")] | sort_by(.updatedAt) | .[-1]' .cleo/contributions/CONTRIBUTIONS.jsonl
Summary statistics jq -s '{
total: length,
complete: [.[] | select(.status == "complete")] | length,
partial: [.[] | select(.status == "partial")] | length,
blocked: [.[] | select(.status == "blocked")] | length,
totalConflicts: [.[].conflictCount] | add
}' .cleo/contributions/CONTRIBUTIONS.jsonl
Completion Checklist
Error Handling
Validation Errors Error Code Message Fix CONTRIB-001Session ID mismatch Use active CLEO session CONTRIB-002Missing marker label Add label to task CONTRIB-005Missing decisions Document all key questions CONTRIB-007Missing rationale/evidence Complete decision objects CONTRIB-011Vague answer language Use concrete, unambiguous answers
Recovery Patterns
jq 'del(._meta.checksum)' .cleo/contributions/T2215.json | sha256sum | cut -c1-16
Missing baseline reference :
jq -s '[.[] | select(.epicId == "T2204")] | .[0]' .cleo/contributions/CONTRIBUTIONS.jsonl
Related Documentation
LOOM Stage Binding (T9670) ct-contribution is bound to LOOM lifecycle stage contribution
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 releasemost epics (work, bug, experiment) Release tag pushed; release manifest recorded testingepics whose kind is release or that gate on IVTR IVT loop converged; ivtLoopConverged: true recorded specificationspec-only epics (no code) Specification accepted; HITL signoff recorded
research → consensus → architecture_decision → specification → decomposition
↓
implementation
↓
validation
↓
testing ← (some epics return here)
↓
release
↓
contribution ← (this skill)
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.mdA 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).
cleo verify T9568 --gate contribution \
--evidence "decision:D-loom-coverage-001;files:.cleo/contributions/T9568-final.json"
cleo complete T9568
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:
