/ct-contribution

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.2
protocol: contribution
adrRefs:
  - ADR-015
  - ADR-053
dependencies: []
sharedResources:
  - subagent-protocol-base
compatibility:
  - claude-code
  - cursor
  - windsurf
  - gemini-cli
license: MIT
metadata:
  version: 1.0.2
  tier: on-demand
  install: harness
  covers:
    - packages/core/src/validation/protocols/cant/contribution.cant
    - packages/core/src/validation/protocols/protocols-markdown/contribution.md
  loomStage: contribution
  lastReviewed: 2026-09-28
  stability: stable

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

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**: 1. Verify epic exists and is active 2. Create contribution task under epic 3. Initialize contribution directories 4. Generate contribution ID 5. Return task ID and setup instructions

**Parameters**: | Parameter | Description | Default | |-----------|-------------|---------| | `<epic-id>` | Parent epic task ID | Required | | `--label` | Marker label for discovery | `consensus-source` | | `--agent` | Agent identifier | Current agent |

`/contribution submit`

Validate and submit the current contribution.

**Usage**:

/contribution submit
/contribution submit --task T2215

**Workflow**: 1. Validate contribution JSON against schema 2. Compute checksum for integrity 3. Append entry to CONTRIBUTIONS.jsonl manifest 4. Update task notes with contribution reference 5. Mark contribution status as `complete` 6. Return submission confirmation

**Parameters**: | Parameter | Description | Default | |-----------|-------------|---------| | `--task` | Contribution task ID | Current focused task | | `--dry-run` | Validate without submitting | false |

`/contribution conflicts [epic-id]`

Detect conflicts between contributions for an epic.

**Usage**:

/contribution conflicts T2204
/contribution conflicts --severity high

**Workflow**: 1. Load all contributions for epic 2. Group decisions by questionId 3. Compare answers for semantic conflicts 4. Classify conflict type and severity 5. Return conflict report with resolution suggestions

**Parameters**: | Parameter | Description | Default | |-----------|-------------|---------| | `[epic-id]` | Epic to analyze | Current scope | | `--severity` | Filter by severity | all |

**Output**:

{
  "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.

**Usage**:

/contribution status
/contribution status T2204

**Workflow**: 1. Query manifest for epic contributions 2. Calculate completion statistics 3. Identify pending conflicts 4. Show consensus progress per question 5. Return status summary

**Output**:

{
  "epicId": "T2204",
  "totalContributions": 3,
  "complete": 2,
  "partial": 1,
  "blocked": 0,
  "conflictsPending": 2,
  "questionsAnswered": 5,
  "consensusReady": false
}

---

Workflow Guides

Starting a New Contribution

# 1. Verify epic exists
ct show T2204

# 2. Initialize contribution
/contribution start T2204 --label rcsd-contrib

# 3. Create contribution task (if not auto-created)
ct add "Session B: Architecture Analysis" \
  --parent T2204 \
  --labels consensus-source,research \
  --phase core

# 4. Start task
ct start T2215

# 5. Create contribution directory
mkdir -p .cleo/contributions

# 6. Generate contribution ID
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,
      "r