collaboration-workflow

Collaboration Workflow Skill

Overview

This skill provides a complete guide to the OpenSquad multi-agent collaboration system. It covers the 4-phase lifecycle with user authorization gates, collaboration board usage, tool calls, and standard message formats for PM, Researcher, and Analyst roles.

Core Rule: User Authorization Required at Every Phase

Each phase must be explicitly approved by the user before proceeding to the next. The PM must present the phase output to the user, wait for confirmation, and only then move forward. Never skip authorization or proceed without user approval.

Phase 1: 确定需求 ──→ 向用户展示需求 ──→ 用户确认 ──→ 进入 Phase 2
Phase 2: 讨论方案 ──→ 向用户展示方案 ──→ 用户确认 ──→ 进入 Phase 3
Phase 3: 开始执行 ──→ 向用户展示进度 ──→ 用户确认 ──→ 进入 Phase 4
Phase 4: 完成验收 ──→ 向用户交付成果 ──→ 用户确认 ──→ 协作结束

When to Use This Skill

Load this skill when:

• Starting a new collaboration session
• Coordinating multiple agents on a shared task
• Writing or reading the collaboration board
• Assigning tasks to team members
• Reporting progress or findings
• Synthesizing research results into a report

Where to Talk: the Task Window, not the Group

Rule: task-related communication stays in the task window. Send to the group only what the user must see — necessary notifications, above all anything that needs their attention or decision.

A collaboration task has its own task window (the collaboration card posted in the group chat opens it). Everything about the task happens there, not in the group:

• Task content → the window: requirements, plan, task assignment, progress, files produced, questions and answers between teammates, delivery notes. Send it as im.send_message(content=..., collab_id="<collab_id>") (files: same call with file_paths=[...]). The task's members and the user read it in the window; the group chat is not touched. Members are woken by a task message, and @<agent_id> in it addresses one of them in particular.
• Anything the user must see or decide goes to the group, not the window: a question, a choice, an approval to give, a blocker, a delivery to accept. The window is the team's own channel — a request for the user left there is a request nobody answers.
• Everyone must be 已参与 before work is handed out: assign_task refuses while any member is still 已邀请 — have each run join_collaboration(card=..., collab_id=...), passing group_id=<the group> when the collaboration's group lives on a paired machine (the board lives there too; without it the join reports join_tracking_failed instead of recording anything) (remind them in the group if needed), then assign.
• The end of the task is announced in the window, not the group: end_collaboration(card=..., collab_id=...) posts the closure into the task thread and wakes the members there. The group only ever held the card that opens the window.
• Everything else → the group: greetings, notices unrelated to the task, topics for the whole group. Send it as im.send_message(content=..., target_id="<group_id>", target_type="group").