skills.rest
faramirezs
faramirezsCOMMUNITY
Explore all skills by this author →
GitHub

kanban-worker

Document pitfalls, edge cases, and best practices for Hermes Kanban workers.

Updated Jun 15, 2026
Search Tags:#handoff#edge-cases#pitfalls#workflows#kanban#guardrails#hermes
One-click install
npx skills add https://github.com/faramirezs/talking_printer --skill kanban-worker-faramirezs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-worker
Source: https://github.com/faramirezs/talking_printer/tree/main/hermes-agent/skills/devops/kanban-worker
Command: npx skills add https://github.com/faramirezs/talking_printer --skill kanban-worker-faramirezs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Kanban workers rely on an auto-injected lifecycle prompt (KANBAN_GUIDANCE). This skill provides deeper detail on pitfalls, edge cases, and best practices to help engineers reason about task handoffs, retries, and task state transitions.

Core Features & Use Cases

  • Comprehensive guidance on Kanban lifecycle edge cases, retries, and debugging handoffs across coding tasks and reviews.
  • Workspace handling guidance for the three workspace kinds: scratch, dir:<path>, and worktree, including tenant isolation best practices.
  • Structured handoff patterns and commands like kanban_complete, kanban_block, and kanban_comment to communicate progress and decisions with deterministic metadata.

Quick Start

Review this guide before running Hermes Kanban tasks to understand common pitfalls and recommended decision points.

Frequently Asked Questions about kanban-worker

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

FAQPage Schema
How do I handle Kanban task handoffs and retries safely?▼

Safe Kanban handoffs and retries require structured commands like kanban_complete, kanban_block, and kanban_comment to communicate task state transitions with deterministic metadata. This prevents silent failures during coding and review handoffs by enforcing predictable runtime decision-making.

What are common Kanban workflow edge cases and pitfalls during deployment?▼

Common Kanban workflow edge cases involve mismanaged task state transitions and debugging handoffs across coding, review, and deployment scenarios. You can mitigate these pitfalls by applying structured guardrails and clear metadata before running tasks.

How do I manage workspace isolation for scratch, dir, and worktree modes?▼

Workspace isolation for scratch, dir:<path>, and worktree modes requires tenant isolation best practices to separate task environments. Properly configuring these workspace kinds prevents cross-task contamination and ensures reliable execution.

When should I use kanban_block versus kanban_comment in task workflows?▼

Use kanban_block when a task hits a runtime barrier requiring external intervention, and kanban_comment to communicate general progress or decisions. Both events ensure deterministic metadata tracking for reliable Kanban state transitions.

Does Hermes Kanban require specific guardrails for reliable task execution?▼

Hermes Kanban requires explicit guardrails for reliable task execution because workers rely on an auto-injected lifecycle prompt. Implementing structured guidance for edge cases and retries ensures safe, predictable operation across all workspace modes.

Related Skills

Explore More Software Engineering Skills→
BarisSozenBarisSozen
1

pitfalls-drizzle-orm

Identify Drizzle ORM migration pitfalls and document safe patterns to prevent schema drift.

Community
Intermediate
jwbaldwinjwbaldwin

work-on-ticket

Fetch Jira ticket details, create a kebab-case branch, and start task planning.

Community
Advanced
MarbleSodasMarbleSodas

kanban-worker

Guide Hermes Kanban workers on lifecycle, workspace, and handoff semantics.

Community
Intermediate
MohamedAbdallah-14MohamedAbdallah-14
3

wz:executor

Validate prerequisites, select interaction mode, and delegate to the execute workflow.

Community
Advanced