aio-kanban-monitorlisted

# Kanban Auto-Dispatch Monitor Watches `.kanban/board.md` for changes. For each task in column `<status>` whose content (as judged by you, inline) contributes to free-text mission `<goal>`, spawns a sub-agent with a full self-contained prompt. Sub-agent owns the task lifecycle (Todo→Doing→Done) — this skill only orchestrates. This skill REQUIRES the v3 kanban storage layout (index board + per-task files). See the `aio-kanban` skill. --- ## Arguments - **`<status>`** (required): one of `Backlog`, `Todo`, `Doing`, `Done`, `Blocked`. Typically `Todo`. - **`<goal>`** (required): free-text mission statement, e.g. `"ship v2 release"`, `"reduce p99 latency under 200ms"`. Used both to filter tasks (you judge relevance) and to anchor the spawned sub-agent's mission. If either is missing, STOP and ask the user. Do NOT guess. --- ## Preconditions (check before starting the loop) 1. `.kanban/board.md` exists. If not → tell user to run `aio-kanban` init first. EXIT. 2. `.kanban/tasks/` directory exists. If not → board is v2, not v3. Tell user to migrate (manually re-init with `aio-kanban`, then re-create tasks as files). EXIT. 3. `fswatch` is installed (the monitor script will exit 3 if not — install via `brew install fswatch`). If missing → tell user how to install, EXIT. 4. `<status>` is one of the allowed columns. If not → STOP, ask user. 5. `<goal>` is non-empty. If not → STOP, ask user. --- ## Algorithm ``` state: dispatched: Set<TaskID> # IDs we've already spawned