kanban-worker

Guides Hermes Kanban workers through task lifecycle pitfalls, handoffs, and retry diagnostics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dispatched Kanban workers often fail at handoffs: they claim cards they never created, write vague block reasons, send useless heartbeats, or repeat the mistakes of prior failed 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 handoff patterns: Concrete kanban_complete summary and metadata shapes for coding, research, and review tasks, including review-required flows that block with structured comments. - Workspace and tenant handling: Rules for scratch, shared directory, and git worktree workspaces, plus tenant-prefixed memory writes to prevent cross-tenant context leaks. - Retry and edge-case diagnostics: How to interpret prior run outcomes (timed_out, crashed, spawn_failed, reclaimed, blocked) and avoid repeating failed approaches. - Use Case: A worker finishes a rate limiter implementation, posts structured metadata as a comment, and blocks with a review-required: reason so a human reviewer can approve and unblock it. ## Quick Start Load the kanban-worker skill and show me how to complete my current Kanban task with a proper summary, metadata, and any cards I created.

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 with proper metadata?

Call kanban_complete with a concise summary and structured metadata such as changed_files, tests_run, and decisions. Shape the metadata so downstream reviewers and aggregators can parse it without re-reading your prose.

How do I hand off a coding task that needs human review?

Post the structured details (changed files, test counts, diff path) as a kanban_comment, then call kanban_block with a reason prefixed 'review-required:'. The reviewer approves and unblocks the task or requests changes via comments.

Why does kanban_complete reject my created_cards list?

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.

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 via kanban_block.

Can I use the hermes kanban CLI inside a worker instead of the tools?

No, the CLI often fails in containerized backends like Docker or Modal because it is not installed there. Use the kanban_* tools, which work across all terminal backends; the CLI exists for human operators.

How do I prevent memory leaks across tenants in Kanban tasks?

When $HERMES_TENANT is set, prefix every persistent memory entry with the tenant namespace, such as 'business-a: Acme is our biggest customer'. Unprefixed entries leak context across tenant boundaries.