kanban-worker

Ensure correct Kanban worker handoffs by structuring kanban_complete outputs with summary, metadata, and created_cards. Validate workspace behavior across scratch, persistent directories, or git worktrees to prevent shared state corruption during multi-agent operations.

Kanban retry attempts fail when workers blindly retry without validating current task state. Use kanban_show to interpret run outcomes and kanban_block with actionable reasons to prevent phantom or unauthorized card claims during edge case handling.

Claim created cards in a multi-tenant Kanban environment by using real kanban_create return values. This ensures tenant isolation and prevents unauthorized claims, maintaining memory integrity across dispatched worker tasks.

Format kanban_complete metadata for downstream parsing by providing a structured summary, precise metadata, and created_cards. This structured output ensures downstream processes can correctly interpret and route the completed Kanban task results.

Use kanban_block instead of retrying when a Kanban task encounters an actionable error. Validate the run outcome with kanban_show first, then provide a specific reason in kanban_block to halt execution safely rather than forcing blind retries.

Yes, this Kanban lifecycle guidance works for git worktree environments. It instructs workers on safe operational behavior across scratch, persistent shared directories, and worktrees to avoid corrupting shared state during multi-agent task execution.