kanban-worker

Guides Hermes Kanban workers through handoffs, retries, and edge cases.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/Lucien-1127/strata-skill --skill kanban-worker-lucien-1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-worker
Source: https://github.com/Lucien-1127/strata-skill/tree/main/kanban-worker
Command: npx skills add https://github.com/Lucien-1127/strata-skill --skill kanban-worker-lucien-1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dispatched Kanban workers often fail silently by producing poor handoffs, hallucinating card IDs, blocking with vague reasons, or retrying blindly after a crash. This Skill provides the deeper operational detail beyond the auto-injected KANBAN_GUIDANCE lifecycle so workers complete, block, and hand off tasks correctly. ## Core Features & Use Cases - Structured Handoffs: Defines good summary and metadata shapes for coding, research, and review tasks, including the review-required block pattern using kanban_comment plus kanban_block. - Workspace and Tenant Handling: Explains how to work in scratch, dir, and worktree workspaces, and how to prefix memory entries with $HERMES_TENANT to prevent cross-tenant leakage. - Retry Diagnostics: Interprets prior run outcomes (timed_out, crashed, spawn_failed, reclaimed, blocked) so retries take a different path instead of repeating failures. - Use Case: A worker finishes a rate limiter implementation, posts structured metadata as a comment, blocks with a review-required reason, and a human reviewer unblocks it after approval. ## Quick Start Load the kanban-worker skill and follow its guidance to complete your current Kanban task with a proper summary, metadata, and heartbeat.

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 Hermes Kanban task correctly?▼

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 terminal; for code changes needing human review, block with a review-required reason instead.

How do I ask a human for input from a headless Kanban worker?▼

Do not call clarify, since headless runs have no live user and the call will time out. Post full context with kanban_comment, then call kanban_block with a one-sentence reason naming the specific decision needed.

What should a Kanban worker do when it is a retry of a failed run?▼

Run kanban_show first and inspect prior runs' outcome, summary, and error fields. Adjust strategy based on the outcome: chunk work after timed_out, reduce memory after crashed, and block for human help after spawn_failed.

Can I claim Kanban cards I created in created_cards?▼

Only pass task IDs captured from successful kanban_create return values. The kernel verifies each ID, and phantom or hallucinated IDs cause the completion to be rejected and permanently recorded on the task's event log.

Why does the hermes kanban CLI fail inside a containerized worker?▼

The CLI is not installed in containerized backends like Docker or Modal. Use the kanban_* tools instead, which work across all terminal backends; the CLI exists only for human operators at a terminal.