team-tasks

Coordinate multi-agent development pipelines by managing tasks, statuses, and agent dispatch.

447|81|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/win4r/team-tasks --skill team-tasks-win4r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-tasks
Source: https://github.com/win4r/team-tasks/tree/main
Command: npx skills add https://github.com/win4r/team-tasks --skill team-tasks-win4r

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate multi-agent development pipelines by managing tasks, statuses, and agent dispatch in a centralized skill.

Core Features & Use Cases

  • Supports linear and dag modes for sequential or parallel task execution, with debate workflow added for multi-agent deliberation.
  • Tracks per-task status, outputs, and logs, and dispatches tasks to agents via sessions_send while keeping a single source of truth.
  • Enables status visibility, ready/graph views, and a debate round workflow including debater management and cross-review prompts.

Quick Start

Initialize a new team-tasks project to orchestrate a multi-agent pipeline across code, test, docs, and monitor agents.

Frequently Asked Questions about team-tasks

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

FAQPage Schema
How do I coordinate multi-agent development pipelines for code, testing, and documentation?

Multi-agent development pipelines are coordinated by managing tasks, statuses, and agent dispatch in a centralized skill, supporting agents like code-agent, test-agent, docs-agent, and monitor-bot for end-to-end project coordination.

What is the difference between linear, dag, and debate workflows in multi-agent task coordination?

Linear and dag modes manage sequential or parallel task execution respectively, while the debate workflow enables multi-agent deliberation with debater management and cross-review prompts for comprehensive decision-making.

How do I initialize and assign tasks across multiple agents in an OpenClaw pipeline?

Initializing an OpenClaw pipeline involves using a production-grade command surface including init, add, assign, and update to dispatch tasks to agents via sessions_send while maintaining a single source of truth.

Can I track task status and generate workflow graphs for multi-agent pipelines?

Task status tracking and workflow graph generation are supported through ready and graph views, alongside per-task output logging and a dedicated log command to monitor pipeline progress.

Does the multi-agent pipeline coordination support cross-review and debate rounds?

Cross-review prompts and debate rounds are fully supported through a dedicated debate workflow that includes debater management, enabling structured multi-agent deliberation before finalizing outputs.

What are the limitations of using a centralized skill for multi-agent task dispatch?

The centralized skill coordinates agents via sessions_send and requires explicit status management using commands like next, ready, and result, meaning pipelines stall if agent statuses are not actively updated and reset.