kanban-worker

Identifies Hermes Kanban worker pitfalls, edge cases, and best practices for dispatches and lifecycles.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Plaidmustache/hermes-nulab --skill kanban-worker-plaidmustache
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanban-worker
Source: https://github.com/Plaidmustache/hermes-nulab/tree/main/skills/devops/kanban-worker
Command: npx skills add https://github.com/Plaidmustache/hermes-nulab --skill kanban-worker-plaidmustache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides deep guidance on Hermes Kanban workers, outlining pitfalls, edge cases, and best practices. The lifecycle (orient → work → heartbeat → block/complete) is auto-injected as KANBAN_GUIDANCE into every worker's system prompt, and this skill exposes deeper detail for targeted scenarios.

Core Features & Use Cases

  • Detailed handoff patterns, diagnostic templates, and edge-case examples for Kanban workers.
  • Workspace and tenancy guidance (scratch, dir:, worktree; tenant isolation) to prevent cross-task leakage and ensure safe state handling.
  • Patterns for kanban_complete, kanban_block, kanban_comment, and related workflows to improve task handoffs and traceability.

Quick Start

Load this skill to review Hermes Kanban worker pitfalls and apply the guidance to your Kanban task workflows.

Frequently Asked Questions about kanban-worker

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

FAQPage Schema
What are the common pitfalls when managing Hermes Kanban worker lifecycles?

Yes, multi-agent Kanban workflows require strict tenant isolation and safe state handling across scratch, dir:, and worktree workspaces. This skill outlines organizational patterns and guardrails to prevent cross-task leakage and ensure reliable collaboration between dispatched workers.

How do I use kanban_block and kanban_complete for task handoffs?

Use kanban_block to halt task execution with diagnostic metadata when encountering edge cases, and kanban_complete to finalize tasks. This skill specifies exact patterns for both commands, improving task traceability and ensuring structured handoffs in Hermes Kanban workflows.

When should I use scratch, dir:, or worktree workspaces for Kanban workers?

Workspace selection depends on isolation requirements: scratch for ephemeral tasks, dir: for directory-specific state, and worktree for branch-safe operations. This skill provides tenancy guidance to prevent cross-task leakage and ensure safe state handling across different dispatch scenarios.

What are the limitations of Hermes Kanban worker retry diagnostics?

Hermes Kanban worker retry diagnostics can fail if structured metadata guidelines are not followed or if worker state leaks across isolated tenants. This skill exposes these limitations and provides diagnostic templates to properly format block conditions and retry logic.

Does the Hermes Kanban worker lifecycle support multi-agent collaboration?

Yes, multi-agent Kanban workflows require strict tenant isolation and safe state handling across scratch, dir:, and worktree workspaces. This skill outlines organizational patterns and guardrails to prevent cross-task leakage and ensure reliable collaboration between dispatched workers.