kanban-worker

Identify and manage edge-case pitfalls for Savarez Kanban workers.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill kanban-worker-anandaanugrahhandyanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanban-worker
Source: https://github.com/AnandaAnugrahHandyanto/savarez_agent/tree/main/skills/devops/kanban-worker
Command: npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill kanban-worker-anandaanugrahhandyanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Kanban Worker skill exposes detailed guidance on common and rare pitfalls that arise when coordinating Kanban teams and automated workers within Savarez. It helps you anticipate handoff issues, retry failures, and workflow quirks so tasks progress reliably.

Core Features & Use Cases

  • Provides deep-dive scenarios and examples for Kanban task lifecycles, including orient, work, heartbeat, block, and complete stages.
  • Clarifies workspace handling modes (scratch, dir:, worktree) and tenant isolation to prevent cross-task data leakage.
  • Describes safe, structured Kanban communications using kanban_complete, kanban_block, and kanban_create with explicit metadata formats.

Quick Start

Load the kanban-worker skill and reference its guidance whenever diagnosing or responding to Kanban task edge-cases across workers.

Frequently Asked Questions about kanban-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle task handoff failures in multi-agent Kanban orchestration?

Task handoff failures in multi-agent Kanban orchestration are managed by identifying edge-case pitfalls and applying structured communications like kanban_block with explicit metadata to ensure reliable task progression across workers.

What is tenant isolation and how does it prevent cross-task data leakage in Kanban workflows?

Tenant isolation in Kanban workflows separates task environments across workers by enforcing specific workspace handling modes, preventing cross-task data leakage during multi-agent orchestration and automated task execution.

How do I use kanban_complete and kanban_block for structured Kanban communications?

Structured Kanban communications use kanban_complete and kanban_block with explicit metadata shapes to safely signal task completion or blockers, ensuring reliable state transitions across multi-agent Kanban workers during orchestration.

What are the workspace handling modes available for Kanban task lifecycles?

Workspace handling modes for Kanban task lifecycles include scratch, dir:, and worktree modes, which manage task environments across orient, work, heartbeat, block, and complete stages to maintain tenant isolation and reliability.

Why do Kanban workers hit edge-case pitfalls during task lifecycles?

Kanban workers hit edge-case pitfalls during task lifecycles due to workflow quirks, retry failures, and handoff issues that arise when coordinating automated teams, requiring structured safety patterns to diagnose and resolve.

When should I use kanban_create in a multi-agent Kanban workflow?

Kanban_create is used in multi-agent Kanban workflows when workers need to spawn new tasks with explicit metadata shapes, ensuring safe structured communication and proper task routing across the orchestration environment.