Cross-Team Collaboration Protocol

Overview

This skill defines the standard protocol for cross-company collaboration in the 6-company OpenClaw enterprise. All agent interactions between companies follow these protocols to ensure consistent, predictable coordination.

When to Use

• When agents from different companies need to collaborate on a task
• When cross-company communication is required for workflow execution
• When multi-company project coordination is needed
• When inter-company resource sharing is required
• Don't use when: Work is within a single company (use internal coordination)

Core Procedures

Cross-Company Communication Protocol

1. Identify Need - Determine which external company capabilities are needed
2. Route Through CEO - Send request to your company's CEO
3. CEO Coordinates - Your CEO contacts the target company's CEO
4. Task Assigned - Target CEO assigns to appropriate agent
5. Execute Work - Agent completes assigned task
6. Quality Gate - Outputs validated by QualityForge
7. Return Results - Results returned through coordination chain

Company Interaction Matrix

Need	Contact Company	Contact CEO	Provides
Development work	DevForge AI	Nexus	Technical implementation
Engineering	DomainForge AI	Orion	Engineering expertise
Infrastructure	InfraForge AI	Orchestrator	Infrastructure services
Creative content	Loopy AI	Vision	Creative deliverables
Quality validation	QualityForge AI	Apex	Quality assurance
Prompt orchestration	PromptForge AI	Sage	Prompt generation and distribution

Conflict Resolution

1. Agent Level: Agents attempt direct resolution
2. CEO Level: Escalate to respective CEOs for coordination
3. Sage Level: If CEOs disagree, escalate to Sage (PromptForge) for mediation
4. Stakeholder Level: Final escalation to project stakeholders

Success Metrics

• Cross-team response time: <2 hours
• Coordination efficiency: ≥95%
• Conflict resolution rate: 100%
• Stakeholder satisfaction: ≥90%

Error Handling

• Error: Target company unavailable Response: Queue task, attempt reconnection, use backup if available
• Error: Cross-company miscommunication Response: Clarify requirements through CEO chain, document communication

Cross-Team Integration

Gigabrain Tags: cross-company, collaboration, coordination, enterprise-orchestration OpenStinger Context: Cross-company session continuity, shared knowledge PARA Classification: Enterprise coordination, cross-team workflows Related Skills: sage-promptforge-chief-architect, nexus-devforge-ceo, apex-qualityforge-ceo Last Updated: 2026-03-04