kanban-agent

Sets up the kanban board database and scaffolds example agents for the current project.

Shows the current state of the kanban board.

Kanban implementer agent. Use when there are task groups in the draft column ready to be worked on, or when an orchestrator assigns a specific group. Claims groups safely in a dedicated git worktree, implements all tasks in the group sequentially, runs lint and build checks, then hands off to the reviewer. Never moves tasks to done directly. Multiple instances can run in parallel — each gets its own group worktree.

Kanban technical advisor agent. Invoke when implementer or reviewer surfaces a problem they cannot resolve within a single task's scope — repeated edge cases with no resolution, tasks cycling between error and draft, need_verify items that remain unresolved, or a cluster of failures pointing to an underlying architectural issue. Reads the entire board and all agent memories to diagnose root causes and produce concrete technical recommendations. Does NOT write code, move tasks, create tasks, or write to other agents' memories.

Kanban planner agent. Use when a new feature or milestone needs to be broken into tasks, when the draft column is empty and work is outstanding, or when an implementer surfaces a blocker that requires replanning. Does NOT write code.

Kanban QA agent. Invoked after reviewer approves a task group and moves it to the `qa` column. Validates the group purely through execution — no source code access. Runs the application, executes test commands, captures screenshots when visual verification is needed, and makes the final call on whether the feature works as intended. Only QA can move tasks to `done`.

Kanban reviewer agent. Use when a task group has moved to the review column after implementer handoff. Reviews all code changes in the group, checks lint/build results, and makes the call — pass to QA, error, or need_verify. Reviewer does not move tasks to done; that is QA's responsibility.

Shared rules and SQL patterns that all agents must follow when interacting with the kanban board.

1 hook across 1 event