teamharness-team-coordination

Plans task boundaries, ownership, and DAG or Loop execution modes for multi-agent team coordination.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple AI workers on a shared project often leads to duplicated work, unclear ownership, hidden dependencies, and noisy status updates. This Skill gives a Leader agent a structured method to decompose work into bounded tasks, assign single owners, choose the right execution mode, and decide when results are truly accepted.

Core Features & Use Cases

  • Execution Mode Selection: Choose between DAG mode for finite, plannable dependency graphs and Loop mode for iterative work that repeats until a stop condition or quality gate is met.
  • Task Boundary Design: Define tasks with one owner, one inspectable output, clear acceptance criteria, and deliverables isolated in shared/tasks/{task-id}/ to prevent write conflicts.
  • Result Acceptance Decisions: After checking a task, decide whether to accept it, request revision, add a verifier task, ask the requester, or report a blocker, so only accepted results unblock downstream work.
  • Use Case: A Leader receives a request to iterate on a research report until it passes review. The Skill guides the Leader to pick Loop mode, plan one iteration at a time, evaluate each round, and report only accepted outcomes to the requester.

Quick Start

Act as the Team Leader and break this project into bounded tasks with clear owners, choosing DAG or Loop mode and defining acceptance criteria before delegating.

Frequently Asked Questions about teamharness-team-coordination

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

FAQPage Schema
How do I coordinate multiple AI agents on one project?

Act as a Leader that breaks work into bounded tasks, each with one owner, one inspectable output, and clear acceptance criteria. Keep dependencies visible, avoid assigning multiple workers to the same deliverable, and report only accepted outcomes to the requester.

When should I use DAG vs Loop execution mode for agent tasks?

Choose DAG when the work is finite and the dependency graph can be planned upfront, such as known phases or fan-out and fan-in work. Choose Loop when work repeats until a stop condition, quality gate, or maximum iteration count, such as build-test-fix cycles.

How should a Leader handle a completed worker task?

A worker completion is not automatic progress. After checking the task, decide whether to accept the result, request a revision through a new task, add a verifier task, ask the requester for clarification, or report a blocker. Only accepted results unblock downstream dependencies.

What makes a good task boundary in multi-agent delegation?

A good task has one owner, one inspectable output, enough context to work independently, no write conflicts with sibling tasks, clear acceptance criteria, and deliverables stored in shared/tasks/{task-id}/. Never assign multiple workers to write the same file or decision record.

When should a Leader not delegate work to workers?

Do not delegate when the goal, acceptance standard, ownership, or safe next step is ambiguous; ask the requester first. Also avoid delegating tasks not returned by ready-node resolution or pre-expanding Loop rounds into a large DAG.