kanban-worker

Name: kanban-worker
Availability: InStock
Author: hungthinh04

Guide Hermes Kanban workers through task completion, blocking, and progress reporting.

Updated May 12, 2026

Search Tags:#workspace #metadata #handoff #kanban #retry #worker #tenancy

Ready to run

npx skills add https://github.com/hungthinh04/Hermes_AI_Agent --skill kanban-worker-hungthinh04

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kanban-worker
Source: https://github.com/hungthinh04/Hermes_AI_Agent/tree/main/skills/devops/kanban-worker
Command: npx skills add https://github.com/hungthinh04/Hermes_AI_Agent --skill kanban-worker-hungthinh04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Hermes Kanban workers execute tasks correctly by clarifying workspace behavior, lifecycle expectations, tenant isolation, and completion or blocking conventions, so handoffs stay consistent and recoverable.

Core Features & Use Cases

Workspace Guidance: Explains how to work safely in scratch, shared directory, and worktree environments.
Handoff Quality: Shows how to write useful summaries and structured metadata for complete and review-required flows.
Operational Guardrails: Covers heartbeats, retry diagnostics, tenant-prefixed memory, and valid created-card claims.
Use Case: Use this Skill when a dispatched worker needs to avoid lifecycle mistakes, format a strong handoff, or decide whether to complete, block, or request review.

Quick Start

Use this skill when you need a Hermes Kanban worker to format its handoff, choose the right lifecycle action, and avoid common pitfalls in workspace, tenant, and retry handling.

Frequently Asked Questions about kanban-worker

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

FAQPage Schema

How do I prevent bad handoffs in Kanban worker runs?▼

Preventing bad handoffs in Kanban worker runs requires writing lifecycle-aware summaries, using structured metadata, and providing explicit block reasons. This ensures dispatched workers format strong handoffs and avoid common lifecycle pitfalls.

How does a dispatched worker handle tasks across scratch, shared directory, and worktree workspaces?▼

Dispatched workers handle tasks across scratch, shared directory, and worktree workspaces by applying workspace-specific file handling and tenant-scoped memory. This workspace guidance ensures safe execution and correct file operations per environment.

When do I need to block or request review in a Kanban worker lifecycle?▼

You need to block or request review in a Kanban worker lifecycle when encountering review-required code changes or operational issues. Explicit block reasons and structured handoff metadata must be provided for downstream automation to resolve correctly.

Does this Kanban worker skill support retry diagnostics and heartbeats?▼

Yes, this Kanban worker skill supports retry diagnostics and heartbeats. It provides operational guardrails that cover heartbeat monitoring and retry diagnostics to ensure dispatched worker runs remain recoverable and avoid lifecycle mistakes.

What is the best way to format tenant-scoped memory and created-card claims for Kanban workers?▼

The best way to format tenant-scoped memory and created-card claims is using tenant-prefixed memory structures and validating created-card claims. This enforces tenant isolation and ensures accurate task tracking across dispatched worker runs.

Why are explicit block reasons needed for downstream automation in Kanban worker handoffs?▼

Explicit block reasons are needed for downstream automation in Kanban worker handoffs because they allow automated systems to understand why a task stopped. This structured metadata prevents handoff mistakes and enables proper retry or review routing.