kanban-worker

Preventing bad handoffs in Kanban worker runs requires writing lifecycle-aware summaries, using structured metadata, and providing explicit block reasons. This ensures dispatched workers format strong handoffs and avoid common lifecycle pitfalls.

Dispatched workers handle tasks across scratch, shared directory, and worktree workspaces by applying workspace-specific file handling and tenant-scoped memory. This workspace guidance ensures safe execution and correct file operations per environment.

You need to block or request review in a Kanban worker lifecycle when encountering review-required code changes or operational issues. Explicit block reasons and structured handoff metadata must be provided for downstream automation to resolve correctly.

Yes, this Kanban worker skill supports retry diagnostics and heartbeats. It provides operational guardrails that cover heartbeat monitoring and retry diagnostics to ensure dispatched worker runs remain recoverable and avoid lifecycle mistakes.

The best way to format tenant-scoped memory and created-card claims is using tenant-prefixed memory structures and validating created-card claims. This enforces tenant isolation and ensures accurate task tracking across dispatched worker runs.

Explicit block reasons are needed for downstream automation in Kanban worker handoffs because they allow automated systems to understand why a task stopped. This structured metadata prevents handoff mistakes and enables proper retry or review routing.