kanban-worker

Clarify ambiguous kanban worker handoffs, retries, and completion decisions.

Updated May 14, 2026
One-click install
npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill kanban-worker-sethypagna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanban-worker
Source: https://github.com/SethyPagna/Secretary-Jarvis/tree/main/src/capabilities/skills/devops/kanban-worker
Command: npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill kanban-worker-sethypagna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity for Jarvis Kanban workers by explaining how to handle task handoffs, workspace rules, retries, progress updates, and completion decisions without losing context.

Core Features & Use Cases

  • Worker Lifecycle Guidance: Explains the orient, work, heartbeat, block, and complete flow that dispatched workers should follow.
  • Workspace Handling: Covers scratch directories, shared persistent folders, and git worktrees so workers know how to read, write, and commit safely.
  • Review and Handoff Patterns: Shows how to format summaries, metadata, blocked reasons, and review-required completions for downstream agents and humans.
  • Isolation and Safety: Describes tenant-prefixed memory, created-card claiming, and retry diagnostics to prevent state leakage and incorrect task closure.

Quick Start

Use this skill when you need a Jarvis Kanban worker to understand its workspace, report progress, and hand off task results with the correct summary and metadata.

Frequently Asked Questions about kanban-worker

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

FAQPage Schema
How do I handle ambiguous task handoffs for dispatched kanban workers?

Kanban worker handoffs are clarified by defining lifecycle steps, workspace handling, and metadata formats so Jarvis-dispatched workers can process coding, research, and review tasks without losing context or state.

What is the correct lifecycle flow for a kanban worker processing tasks in git worktrees?

The kanban worker lifecycle follows an orient, work, heartbeat, block, and complete flow, ensuring workers safely read, write, and commit within scratch directories, shared folders, and git worktrees.

How do kanban workers report blocked tasks and review-required completions?

Workers format blocked reasons, summaries, and review-required completions using defined metadata handoff patterns, ensuring downstream agents and humans receive structured progress updates for review tasks.

How does tenant isolation prevent state leakage during kanban worker retries?

Tenant isolation uses tenant-prefixed memory, created-card claiming, and retry diagnostics to prevent state leakage and incorrect task closure across shared persistent folders and scratch directories.

Does this kanban worker skill require specific dependencies or component setups?

No dependencies or components are required. The skill provides guidance for Jarvis-dispatched workers operating across git worktrees and shared folders without needing external modules or additional environment setup.

What are the limitations of using scratch directories for kanban worker workspace handling?

Scratch directories provide isolated workspace handling but require careful tenant-prefixed memory management and created-card claiming to prevent state leakage and ensure safe commits across git worktrees.