kanban-worker

Task handoffs in a multi-agent Kanban workflow require structured summary formatting and metadata capture to maintain context. Workers must follow lifecycle guidance to orient, work, heartbeat, block, or complete tasks while applying tenant-safe memory prefixing.

Formatting worker handoffs for coding and research tasks involves using specific summary and metadata shapes. This ensures clean handoff quality patterns that capture progress, workspace differences, and blocking reasons for human review when necessary.

Kanban workers recover from failed runs by interpreting blocked, archived, timed out, crashed, or spawn-failed statuses. The worker lifecycle guidance helps them respond appropriately to these failure states and decide whether to retry or escalate.

A Kanban worker should block a task for human review when dealing with code changes requiring oversight, rather than completing docs-only tasks directly. This decision relies on evaluating workspace differences and applying completion versus blocking rules.

Managing workspaces in a multi-agent Kanban system involves understanding scratch, shared directory, and worktree behavior. Workers must apply tenant-safe memory prefixing to isolate data and ensure operational safety across different spawned runs.

Multi-agent task management with worker heartbeats requires no external dependencies. The skill provides built-in operational requirements for summary formatting, metadata capture, and lifecycle decisions within the existing workflow.