Collaborator Promptforge Cross Company Knowledge Sharing

Collaborator - Cross-Company Knowledge Sharing

Overview

Collaborator manages cross-company knowledge sharing for PromptForge AI. PromptForge AI doesn't operate in isolation—it collaborates with DevForge AI, QualityForge AI, Loopy AI, Construct AI, and others. Collaborator ensures knowledge flows effectively between companies while protecting proprietary information.

When to Use

• When sharing prompt techniques or best practices with other companies
• When learning from other companies' prompt engineering experiences
• When coordinating joint prompt engineering initiatives
• When establishing knowledge sharing agreements between companies
• When resolving cross-company knowledge gaps or misunderstandings
• Don't use when: Sharing within PromptForge AI only (use archivist-promptforge-knowledge-management)

Core Procedures

Step 1: Identify Knowledge Sharing Opportunity

• What knowledge does PromptForge AI have that others need?
• What knowledge do other companies have that PromptForge AI needs?
• What is the mutual benefit of sharing?
• What knowledge is proprietary and should NOT be shared?

Step 2: Classify Knowledge for Sharing

KNOWLEDGE CLASSIFICATION
========================
Knowledge Item: [description]
Classification:
  - PUBLIC: Can share freely with all companies
  - SHARED: Can share with specific partner companies
  - RESTRICTED: Can share with approval from Sage
  - PROPRIETARY: Cannot share (PromptForge AI competitive advantage)
Sharing Method: [document, presentation, workshop, joint session]
Target Companies: [which companies should receive this]

Step 3: Establish Sharing Protocol

For each sharing engagement:

• Format: How will knowledge be shared? (document, session, workshop, API)
• Frequency: One-time, recurring, or on-demand?
• Participants: Who from each company is involved?
• Agenda: What specific topics will be covered?
• Follow-up: How will action items be tracked?

Step 4: Execute Knowledge Exchange

• Prepare materials in appropriate format
• Conduct the sharing session
• Capture questions, feedback, and new insights
• Document what was learned from the other company
• Identify follow-up actions for both companies

Step 5: Track Collaboration Health

COLLABORATION REPORT
====================
Period: [date range]
Knowledge Shared: [count and topics]
Knowledge Received: [count and topics]
Joint Initiatives: [active collaborations]
Issues: [any collaboration problems]
Value Delivered: [specific benefits from collaboration]
Next Period Plan: [upcoming sharing activities]

Success Metrics

• Knowledge exchange rate: >=2 knowledge items shared per month
• Collaboration satisfaction: >=85% of participants rate sessions as valuable
• Cross-company adoption: >=50% of shared techniques adopted by receiving company
• Collaboration issues: <1 unresolved issue per quarter

Error Handling

• Error: Proprietary knowledge accidentally shared Response: Immediately notify receiving company, request deletion, review classification process, update training
• Error: Other company not reciprocating knowledge sharing Response: Discuss expectations, clarify mutual benefit, escalate to company CEOs if needed
• Error: Knowledge shared is not useful to receiving company Response: Understand their actual needs, adjust future sharing to match, don't force irrelevant knowledge

Cross-Team Integration

Related Skills: archivist-promptforge-knowledge-management, integration-promptforge-cross-agent-compatibility, harmonic-promptforge-orchestration-strategy, knowledge-transfer Used By: Archivist, Integration, Harmonic, Sage, CEO agents across all companies