kanban-worker

Guides Hermes Kanban workers through task handoffs, retries, and workspace handling.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill kanban-worker-reimonsk8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-worker
Source: https://github.com/Reimonsk8/hermes-9router-model-balancing/tree/main/scripts/skills/devops/kanban-worker
Command: npx skills add https://github.com/Reimonsk8/hermes-9router-model-balancing --skill kanban-worker-reimonsk8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dispatched Kanban workers often mishandle task handoffs, claim cards they never created, send useless block reasons, or repeat the mistakes of failed prior runs. This Skill provides the deeper operational detail beyond the auto-injected lifecycle guidance so workers complete, block, and hand off tasks correctly. ## Core Features & Use Cases - Structured handoffs: Patterns for kanban_complete summaries and metadata shaped for coding, research, and review tasks, including review-required blocking flows. - Retry diagnostics: Interprets prior run outcomes (timed_out, crashed, spawn_failed, reclaimed, blocked) so retries take a different path instead of repeating failures. - Workspace and tenancy rules: Correct behavior for scratch, shared directory, and git worktree workspaces, plus tenant-prefixed memory isolation. - Use Case: A worker dispatched to fix a rate limiter finishes with 14 passing tests, posts structured metadata as a comment, and blocks with a review-required: reason so a human reviewer can approve before merge. ## Quick Start Load this skill when dispatched as a Kanban worker and follow its handoff, heartbeat, and retry patterns for your assigned task.

Frequently Asked Questions about kanban-worker

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

FAQPage Schema
How do I complete a Kanban task as a Hermes worker agent?▼

Call kanban_complete with a concise summary and structured metadata such as changed_files, tests_run, and decisions. Only complete when the task is genuinely finished; otherwise block with a specific reason so a human can respond.

How should a Kanban worker handle code changes that need human review?▼

Post the structured metadata (changed files, test counts, diff path) as a kanban_comment first, then call kanban_block with a reason prefixed 'review-required:'. The reviewer approves via hermes kanban unblock, which re-spawns you with the comment thread.

What should I do when a Kanban task run is a retry?▼

Run kanban_show first and inspect prior runs' outcome, summary, and error fields. Outcomes like timed_out, crashed, or spawn_failed each indicate different fixes, such as chunking work, reducing memory, or asking a human instead of retrying blindly.

Why does claiming created cards fail on kanban_complete?▼

The kernel verifies every id in created_cards exists and was created by your profile. Only pass ids captured from successful kanban_create return values; hallucinated or reused ids cause the completion to be rejected and logged.

Can I use the hermes kanban CLI inside containerized worker backends?▼

The CLI is not installed in Docker, Modal, or SSH terminal backends, so it will fail there. Use the kanban_* tools from inside the agent instead; the CLI exists for human operators at a terminal.