Kanban Automations

Durable Cursor-like automations via VibeOS kanban.

Skill metadata

Source	Bundled (installed by default)
Path	skills/devops/kanban-automations
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos
Tags	kanban, automations, multi-agent, cursor, devops
Related skills	project-kanban-worktrees, cursor-task-orchestration, vibeos-local-verify-deploy

Reference: full SKILL.md

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Kanban Automations

Use the kanban board when work must survive process restart, span profiles, or run as a queue — the VibeOS analogue of Cursor Automations / long Task runs. Prefer delegate_task only for short in-session parallelism (cursor-task-orchestration).

When to Use

• Bugfix / docs / refactor queues across sessions
• Multi-profile workers (coding vs research vs ops)
• Project-linked worktrees (project-kanban-worktrees)
• User says “поставь в очередь”, “автоматизация”, “как Automations”

Prerequisites

• kanban.journal_mode: delete (default; required on macOS APFS)
• Dispatcher: gateway with kanban.dispatch_in_gateway: true or standalone dispatcher service
• Optional: vibeos project bind-board <slug> <board>

How to Run

vibeos kanban init
vibeos kanban create --title "Fix X" --assignee coding
vibeos kanban list
vibeos kanban show <id>
# after worker finishes:
vibeos kanban complete <id>

For project worktrees:

vibeos project show <slug>
vibeos project bind-board <slug> <board>
# create task linked to project — branch/worktree naming is automatic

Quick Reference

Recipe	Pattern
Bugfix queue	tasks triage → assign coding → verify → complete
Docs refresh	assignee with docs-focused description; no deploy unless asked
Parallel features	one task per slice; bind project for .worktrees/<task-id>
In-session only	do not use kanban — use delegate_task

Useful verbs: create, list/ls, show, assign, comment, complete, block, unblock, archive, tail, stats.

Procedure

1. Confirm board + journal mode (delete).
2. Create small tasks (one outcome each); put acceptance criteria in the body.
3. Assign a profile that matches the work (coding for IDE/repo work).
4. Let dispatcher claim; watch with vibeos kanban tail / show.
5. On failure limit, task auto-blocks — fix cause, unblock, retry.
6. Durable success → complete / archive; do not leave zombies.

Pitfalls

• Enabling TermitPro stub plugins does not create a board
• WAL journal on macOS caused double-claim issues — keep delete
• kanban_* tools stay schema-free in normal chat (check_fn); workers get them when spawned for a task
• Do not git push from workers under no-github policy

Verification

• Task moves to done with a completed run
• Worker log exists for the run (vibeos kanban log / runs)
• Project tasks use <slug>/<task-id> branches when bound