c2c

Coordinate Claude-to-Claude sessions with pre-launch Reframe checks and standardized artifacts.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/disabledbydesign/cyborg-methodologies --skill c2c
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: c2c
Source: https://github.com/disabledbydesign/cyborg-methodologies/tree/main/c2c
Command: npx skills add https://github.com/disabledbydesign/cyborg-methodologies --skill c2c

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

C2C-Praxis-Attractor enables Claude-to-Claude collaborative sessions oriented toward praxis rather than consensus, handling session launch, handoff generation, and session state checks. Reframe must be active before launching any session to ensure robust critique and prevent convergence bias.

Core Features & Use Cases

  • Session launch: creates and manages CONVERSATION.md, launches inter-instance workflows, and enforces pre-launch Reframe checks.
  • Handoff generation: outputs peer-to-peer handoff documents that preserve uncertainty-forward critique and decision context.
  • Session state review: supports ongoing monitoring of session progress, decisions, and standing questions across cycles.

Quick Start

Start a C2C session by telling Claude to run /c2c start <session-name>.

Frequently Asked Questions about c2c

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate Claude-to-Claude collaboration sessions without converging on consensus?

Claude-to-Claude collaboration is coordinated through structured session launches that maintain praxis-oriented critique. The system enforces a pre-launch Reframe check to prevent convergence bias and ensures robust critique across multiple agents.

What is a Reframe check in multi-agent session management?

A Reframe check is a blocking pre-launch governance step required before starting any Claude-to-Claude session. It ensures robust critique is established and prevents convergence bias by setting up the praxis-oriented framework before inter-instance workflows begin.

How do I generate handoff documents for Claude-to-Claude sessions?

Handoff documents are generated as peer-to-peer artifacts that preserve uncertainty-forward critique and decision context. The generation process outputs standardized documents to transfer session state and standing questions between Claude instances.

How do I start a Claude-to-Claude collaborative session?

To start a Claude-to-Claude session, instruct Claude to run the start command with your desired session name. This creates and manages the conversation file, enforces the pre-launch Reframe check, and scaffolds the inter-instance workflow.

What artifacts are created when managing Claude-to-Claude session state?

Session state management creates standardized artifacts including CONVERSATION.md for tracking inter-instance workflows and SKILL_FEEDBACK.md for governance. These files support ongoing monitoring of session progress, decisions, and standing questions across cycles.

Can I monitor session progress and decisions across multiple Claude agents?

Session state review supports ongoing monitoring of progress, decisions, and standing questions across multiple Claude agents. The governance surface tracks these cycles through standardized artifacts to maintain continuity throughout the collaboration.