kanban-workerlisted

# Kanban Worker — Pitfalls and Examples You're seeing this skill because you're running as a kanban worker — `$VEXIS_KANBAN_TASK_ID` is set in your environment, and the dispatcher spawned this process to work on one specific card. Your job: orient → work → declare outcome (`vexis-kanban complete` OR `vexis-kanban block`) → exit cleanly. ## Always orient first Before doing anything, read your card. The dispatcher might have claimed you while the user changed the body, blocked the task, or archived it: ```bash vexis-kanban show "$VEXIS_KANBAN_TASK_ID" --json ``` If `status` came back `blocked` or `archived`, **stop**. You shouldn't be running. Exit without calling complete. If you see `runs[]` with prior closed runs, **you're a retry**. The previous `outcome` + `summary` + `error` tell you what didn't work. Don't repeat that path. ## Workspace handling Your card has `workspace_kind` and `workspace_path`: | Kind | What it is | How to behave | |---|---|---| | `dir` (default) | An absolute path to a real directory; persistent | Treat it like long-lived state. Other workers will read what you write. | | `scratch` | Fresh tmp dir, yours alone | Read/write freely; gets garbage-collected when the card is archived. | `cd` into `workspace_path` first if it's set — your CWD on spawn is the daemon's workspace, not the card's. ## Good summary + metadata shapes The `summary` field on `vexis-kanban complete` is what downstream cards (and humans) read. Be structured. **Coding wor