kanban-worker

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

Updated May 28, 2026
One-click install
npx skills add https://github.com/patty-chow/the-stable --skill kanban-worker-patty-chow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-worker
Source: https://github.com/patty-chow/the-stable/tree/main/skills/devops/kanban-worker
Command: npx skills add https://github.com/patty-chow/the-stable --skill kanban-worker-patty-chow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Dispatched Kanban workers often fail silently by producing bad handoffs, claiming phantom cards, blocking with vague reasons, or repeating 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 examples of kanban_complete summaries and metadata shapes for coding, research, and review tasks, including review-required blocking flows. - Workspace and tenant handling: Rules for scratch, shared directory, and git worktree workspaces, plus tenant-prefixed memory isolation. - Retry and failure diagnostics: How to interpret prior run outcomes (timed_out, crashed, spawn_failed, reclaimed) and avoid repeating failed paths. - Codex lane integration: Optional isolated implementation lane using Codex CLI in a git worktree, with reconciliation checklists and metadata schema. - Use Case: A worker dispatched to fix a rate limiter completes with structured metadata (changed files, test counts, decisions), claims only verified created cards, and blocks with a specific review-required reason so a human can approve the merge. ## Quick Start Load the kanban-worker skill and follow its handoff and blocking patterns to complete your dispatched Kanban task with structured metadata.

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 structured metadata?▼

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

When should a Kanban worker block instead of complete?▼

Block when work needs human review or a decision, using a reason prefixed with 'review-required: ' for code changes. Put detailed context in a kanban_comment first, since kanban_block only carries the human-readable reason.

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.

How do I handle a retry of a previously failed Kanban task?▼

Run kanban_show first and inspect prior runs' outcome, summary, and error fields. Adjust your approach based on the failure type, such as chunking work after a timeout or reducing memory after a crash, instead of repeating the same path.

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

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

When should I use the Codex lane for a Kanban coding task?▼

Use it only for bounded coding or refactor tasks with clear acceptance criteria where the repo can be isolated in a git worktree and Hermes can rerun tests independently. Skip it for research tasks, secret-touching changes, or edits faster done directly.