event-coordination

Event-Driven Coordination

This skill provides the event-driven coordination model for teamwork v3 orchestrators. It replaces the v2 polling-based monitoring loop with native Claude Code hooks.

---

How Hooks Work

Claude Code provides two lifecycle hooks that enable event-driven orchestration:

Hook	Trigger	Purpose
TaskCompleted	A task's status changes to completed	Track project progress, detect completion
TeammateIdle	A teammate finishes its current work	Detect available workers for task assignment

Hook Execution Flow

Event occurs (e.g., task completed)
    |
    v
Claude Code fires hook
    |
    v
Plugin hook script runs (project-progress.js or teammate-idle.js)
    |
    v
Hook script outputs context information to stdout
    |
    v
Context is injected into the orchestrator's conversation
    |
    v
Orchestrator takes action based on context

Hooks do NOT take actions directly. They provide context that enables the orchestrator to make informed decisions.

---

TaskCompleted Hook

What It Does

When any task is marked as completed, project-progress.js runs and outputs the current project progress:

Progress: 4/7 completed, 2 in progress, 1 pending.

Or when all tasks are done:

All 7 tasks completed. Ready for final verification.

Orchestrator Response

The orchestrator receives this context and decides:

• More tasks remain: Continue waiting, or spawn additional workers if needed
• All tasks done: Spawn the final verifier

# When hook reports all tasks completed
Task(
    subagent_type="teamwork:final-verifier",
    team_name="<team>",
    name="verifier",
    prompt="Verify project completion: run full build, full test suite, check all evidence..."
)

---

TeammateIdle Hook

What It Does

When a teammate becomes idle, teammate-idle.js runs and reports whether unassigned tasks are available:

worker-backend idle. 3 unassigned tasks available.