kanban-worker

Multi-agent Kanban workflows require structured handoffs using kanban_complete and kanban_block to avoid coordination gaps. Enforcing a documented lifecycle of orient, work, heartbeat, block, and complete keeps dispatched workers progressing reliably across shared tasks.

The Kanban worker lifecycle follows four phases: orient, work, heartbeat, and block or complete. This structured progression ensures agents handle tasks systematically, using retries and heartbeats to maintain safe progress before performing structured handoffs.

Preventing cross-tenant data leakage requires tenancy-aware memory scoping and workspace isolation practices. Using distinct workspace kinds like scratch, dir:<path>, and worktree ensures agents operate within isolated boundaries during task handoffs.

Use kanban_block when a worker hits an unrecoverable edge case or failed retry, and kanban_complete when the task finishes successfully. Both enforce structured handoffs by shaping metadata appropriately for downstream readers or reviewers.

Yes, this Kanban guidance explicitly covers cross-agent collaboration, including task handoffs and reviewer interactions. It provides patterns for multi-agent coordination to ensure safe progress and clear communication across the worker lifecycle.