event-coordination

Replace polling loops with TaskCompleted and TeammateIdle hooks for teamwork orchestrators.

4|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/mnthe/hardworker-marketplace --skill event-coordination
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-coordination
Source: https://github.com/mnthe/hardworker-marketplace/tree/main/plugins/teamwork/skills/event-coordination
Command: npx skills add https://github.com/mnthe/hardworker-marketplace --skill event-coordination

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Event-driven coordination eliminates the need for polling loops in teamwork orchestrators by introducing native hooks that react to events such as TaskCompleted and TeammateIdle.

Core Features & Use Cases

  • Event-driven orchestration for teamwork v3, replacing schedule-based polling with immediate hook-driven updates.
  • Hooks: TaskCompleted to track progress and trigger next steps; TeammateIdle to detect available workers and balance workload.
  • Use Case: In a multi-worker project, as tasks complete, the orchestrator can instantly reassign work and launch the final verification when everything is done.

Quick Start

Enable the event-coordination skill in your Claude Code environment, configure the two hooks, and run a test workflow to observe real-time task progress updates.

Frequently Asked Questions about event-coordination

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

FAQPage Schema
How do I replace polling loops with event-driven hooks for teamwork orchestration?

Event-driven orchestration replaces polling loops by using TaskCompleted and TeammateIdle hooks to emit context to the orchestrator for immediate decision-making. Tasks finishing or workers going idle trigger instant updates instead of scheduled checks.

What is the best way to track real-time task progress in a multi-worker orchestrator?

Real-time task progress tracking is handled by the TaskCompleted hook, which fires as tasks finish and notifies the orchestrator to trigger next steps or launch final verification when all work is done.

How do I detect idle workers and rebalance workload in an event-driven workflow?

The TeammateIdle hook detects available workers and emits their context to the orchestrator, enabling immediate workload rebalancing and task reallocation without relying on schedule-based polling.

Does event-coordination work with v3 orchestrators that have multiple workers?

Yes, the skill is specifically applicable to v3 orchestrators with multiple workers, providing native TaskCompleted and TeammateIdle hooks for real-time task progress and reallocation scenarios.

How do I set up event-driven coordination hooks in my workflow?

Enable the event-coordination skill in your Claude Code environment, configure the two hooks, and run a test workflow to observe real-time task progress updates and worker reallocation.

Why should I use event-driven hooks instead of schedule-based polling for task coordination?

Event-driven hooks eliminate polling loop overhead by providing immediate, context-rich updates when tasks complete or workers go idle, allowing the orchestrator to reassign work instantly and launch verification upon completion.