Role Collaboration

📖 Best for: Business leaders, department managers, and complex task orchestrators

📖 Reading time: about 8 minutes

📖 In one sentence: Form a team of digital employees by business relationship and let them divide work and collaborate like a real company.

Digital employees are YingCore's single-combat unit—one role, one skill set, one persona. But enterprise-grade business can never be completed by a single fighter: after writing an article you still need design and visual assets, and after publishing you need data analysis. This is where role collaboration comes in: let multiple digital employees divide work, cooperate, and review each other like a real team, expanding one type of task output into a full business chain.

Core Idea: From Tools to Teams

YingCore's collaboration mechanism turns digital employees from isolated tools into a digital mirror of real business teams:

Collaboration is not simple sequential calls. It is a role network with business relationships—the four patterns of supervise, relay, parallel, and feedback cover all real business scenarios.

Four Collaboration Patterns

The collaboration between digital employees can be summarized into four basic patterns. Complex business flows are combinations of them:

Pattern	Relationship	Use Case	Typical Example
🎯 Supervise	Manager assigns tasks to executors	Approval flow, task dispatch	Operations manager → multiple content creators
🔀 Relay	A finishes, hands to B	Strongly dependent flow	Research → Writing → Proofreading
⚡ Parallel	Multiple roles work simultaneously	Tasks that can be split with no dependency	Produce copy, posters, and video script at once
🔁 Feedback	B reviews A, A edits and resubmits	Quality check loop	Drafting → Review → Editing → Final approval

Supervise Example

The manager role assigns tasks to multiple executor roles, and all results return to the manager:

# Operations manager dispatches tasks to 3 content creators
orchestration:
  type: supervise
  manager: operations-manager
  workers:
    - role: content-creator-xiaohongshu
      task: write a product seed article
    - role: content-creator-zhihu
      task: write an in-depth review
    - role: content-creator-video-script
      task: write a 60-second voice-over script

Feedback Example

Drafting and review form a closed loop, cycling until final approval passes:

orchestration:
  type: feedback
  loop:
    - role: writer
      output: draft
    - role: reviewer
      action: check quality
    - role: writer
      action: revise based on feedback
      condition: triggered when review fails
  exit:
    - role: final-reviewer
      condition: review passes

Core Mechanisms: Four Collaboration Building Blocks

Digital employee collaboration is built on four mechanisms:

1️⃣ Role Dispatcher

Routes tasks to the most suitable digital employee, supporting three strategies:

Strategy	Rule	When to Use
Capability match	Pick the role whose skill set matches best	General scenarios
Load balancing	Pick the role with the fewest current tasks	High concurrency
Round robin	Distribute in order	Fair distribution

2️⃣ Shared Context

All roles share the same business context during collaboration, avoiding information silos:

{
  "context": {
    "project_id": "campaign-2025-q3",
    "brand": "Quick Cloud",
    "target_audience": "SMB CTOs",
    "previous_outputs": [
      { "role": "researcher", "summary": "3 customer pain points..." },
      { "role": "planner", "summary": "content topic matrix..." }
    ]
  }
}

3️⃣ Collaboration Kanban

Visualizes the status, owner, and progress of all collaboration tasks, like a project management view:

4️⃣ Message Bus

Real-time communication between roles, supporting both synchronous wait and async notification:

Message Type	Purpose	Example
📤 Task dispatch	Manager → executor	Please finish this seed article within 2 hours
📥 Result return	Executor → manager	Done, 1200 words total
🆘 Help request	Any → Any	Need brand assets, please push
✅ Confirmation	Any → Any	Got it, will reply within 30 minutes

Complete Scenario: Content Marketing Department

A brand is running a Q3 marketing campaign that requires 5 digital employees to collaborate:

Step	Role	Input	Output
1	Marketing Manager	Business goal	Task assignment list
2	Content Planner	Business goal	Topic list, key info
3	Copywriter	Topic list	3 draft articles
4	Designer	Topic list	Visuals, posters
5	Content Reviewer	Copy + visuals	Final draft / revision notes
6	Channel Publisher	Final draft	Multi-channel publish
7	Data Analyst	Post-publish data	Performance report

Full YAML configuration:

# content-marketing-team.yaml
team: marketing-department
orchestration:
  - id: step-1
    role: marketing-manager
    action: analyze business goal, output task list
    output: task-list.json

  - id: step-2
    role: content-planner
    depends_on: [step-1]
    action: output topic matrix based on task list
    output: topics.json

  - id: step-3
    role: copywriter
    depends_on: [step-2]
    action: write copy for each topic
    output: drafts/*.md

  - id: step-4
    role: designer
    depends_on: [step-2]
    action: produce visuals for each topic
    output: assets/*.png
    parallel_with: [step-3]

  - id: step-5
    role: content-reviewer
    depends_on: [step-3, step-4]
    action: review copy and visuals
    on_fail: feed back to step-3 or step-4 for revision
    loop_until: pass

  - id: step-6
    role: channel-publisher
    depends_on: [step-5]
    action: sync to multiple channels
    output: publish-link-list

  - id: step-7
    role: data-analyst
    depends_on: [step-6]
    delay: 7d
    action: collect data and generate report
    output: report.pdf

Key Parameters

Parameter	Type	Description
`team`	string	Collaboration team name
`orchestration`	array	Collaboration step list
`depends_on`	array	Upstream step IDs this step depends on
`parallel_with`	array	Step IDs that can run in parallel
`loop_until`	string	Loop exit condition
`delay`	duration	Step start delay
`on_fail`	string	Fallback action on failure

Best Practices

Practice	Description
🎯 Keep role responsibility single	One role handles one kind of output, avoid catch-all roles
🔀 Use relay for critical path	Strongly dependent steps run sequentially for quality
⚡ Use parallel for independent tasks	Run dependency-free steps simultaneously to save time
🔁 Add feedback for quality	Key outputs must have a review step, loop until qualified
👤 Reserve key decisions for humans	Strategic and brand-tone soft judgments go to human employees
📊 Visualize collaboration chain	Use kanban so everyone sees who is doing what
🛑 Set fallback roles	Every task has an emergency takeover role
💰 Control collaboration depth	Keep one chain to 7 or fewer roles, split if larger

Next Steps

Role collaboration makes multiple roles cooperate horizontally; task orchestration makes multiple steps link vertically. Learn more about Workflow and Task Orchestration, including 5 orchestration patterns and exception handling.

Core Idea: From Tools to Teams​

Four Collaboration Patterns​

Supervise Example​

Feedback Example​

Core Mechanisms: Four Collaboration Building Blocks​

1️⃣ Role Dispatcher​

2️⃣ Shared Context​

3️⃣ Collaboration Kanban​

4️⃣ Message Bus​

Complete Scenario: Content Marketing Department​

Key Parameters​

Best Practices​

Next Steps​