team-coordination

Structure multi-agent team work into DAGs or loops with quality gates.

5.3k|652|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill team-coordination-agentscope-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-coordination
Source: https://github.com/agentscope-ai/HiClaw/tree/main/manager/agent/team-leader-agent/skills/team-coordination
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill team-coordination-agentscope-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of getting team work organized and convergent when multiple Workers contribute different outputs, with unclear ownership, acceptance criteria, and replanning needs.

Core Features & Use Cases

  • Execution-mode strategy (DAG vs Loop): Selects a finite dependency graph approach or an iterative quality-improvement loop based on the work’s shape and stopping conditions.
  • Context-bound task design: Defines task boundaries by ownership, independent context, non-overlapping writes, and inspectable outputs to enable safe parallelism.
  • Quality gates and result acceptance: Turns Worker results into candidates and then explicitly decides whether to accept, verify, repair, ask, or replace plan structure.
  • Interruption and replanning workflow: Provides a controlled pause/stop decision flow with confirmation and safe reuse rules for accepted dependency inputs.

Quick Start

Use the team-coordination skill to design a DAG or Loop with acceptance criteria, parallelism boundaries, and replan/verification rules before calling project-management or task-management.

Frequently Asked Questions about team-coordination

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

FAQPage Schema
How do I structure multi-agent project planning to ensure tasks converge?

Multi-agent project planning converges by structuring collaborative work into DAGs or loops with clear task waves, ownership boundaries, and explicit quality gates. This approach ensures independent workers contribute outputs that meet defined acceptance criteria.

When should I use a DAG vs a loop for task delegation in agent collaboration?

Use a DAG for task delegation when work has finite dependencies and a clear stopping condition, whereas an iterative loop is better suited for scenarios requiring continuous quality-improvement cycles before reaching the final acceptance standard.

How do I set quality gates and acceptance criteria for worker outputs?

Quality gates turn Worker results into candidates, requiring an explicit decision to accept, verify, repair, ask, or replace the plan structure. Acceptance criteria are set by defining done standards and partitioning work by non-overlapping writes.

What is the best way to handle replanning and human intervention during team work?

Replanning and human intervention require a controlled pause or stop decision flow with confirmation. You must apply safe reuse rules for accepted dependency inputs before adjusting the project-management structure.

Can I partition tasks for parallel execution without overlapping context?

Yes, you partition tasks by defining boundaries based on ownership, independent context, non-overlapping writes, and inspectable outputs. This context-bound task design enables safe parallelism across multiple workers.