kanban-worker

Guide Hermes Kanban workers to complete or block tasks with parseable handoffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps Hermes Kanban workers complete tasks correctly by preventing common handoff mistakes, workspace pitfalls, tenant data leaks, and failure-mode errors.

Core Features & Use Cases

  • Workspace-safe behavior: Guidance for scratch, persistent dir, and git worktree workspaces so you don’t corrupt shared state.
  • Tenant isolation: Rules for namespacing persistent memory to avoid cross-tenant context leakage.
  • Correct completion semantics: Clear when to use complete vs block, how to shape summaries/metadata for downstream tooling, and how to claim only real created card IDs.
  • Operational edge-case handling: Retry diagnostics (timed out, crashed, spawn failed, reclaimed/archived, blocked) and heartbeat quality expectations.
  • Examples for downstream parsing: Practical metadata shapes that reviewers, dashboards, and aggregators can reliably consume.

Quick Start

Load the kanban-worker skill while running a Hermes Kanban dispatcher worker to follow the provided lifecycle, workspace, and handoff rules for the current task.

Frequently Asked Questions about kanban-worker

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

FAQPage Schema
How do I structure Kanban worker handoffs for reliable downstream parsing?

To complete Kanban tasks correctly, use complete when finished or block when stalled, claim only real created card IDs, and shape summaries for downstream tooling. This prevents invalid completion states and ensures reliable handoffs across worker execution scenarios.

How do I isolate tenant memory in Kanban worker execution?

Guarded tool usage prevents invalid Kanban completion states by restricting actions that could corrupt shared state or leak tenant data. Apply strict rules during worker execution to ensure correct task completion and reliable handoffs across all workspace types.

How do I handle Kanban retry diagnostics for timed out or crashed tasks?

Kanban workers safely operate across scratch, persistent directories, and git worktrees by following workspace-safe behavior rules. This prevents corrupting shared state during task execution and ensures reliable handoffs across different working directory configurations.

When should I block vs complete a Kanban task during worker execution?

Block a Kanban task when stalled or encountering failure modes, and complete it when finished successfully. Correct completion semantics require claiming only real created card IDs and shaping metadata properly to avoid invalid completion states during worker handoffs.