Skip to content

Claude Code plugin skills

The Claude Code Kanban plugin adds three skills to Claude Code, and it sends your board moves to the session. claude-code-kanban --install installs the plugin, together with its hooks. See Getting started.

In Claude Code the skills have the plugin name as a prefix:

Skill Who can start it What it does
/claude-code-kanban:kanban You or Claude Runs the board’s CLI: links docs, adds panes, opens and pins sessions.
/claude-code-kanban:dispatch You or Claude Starts other sessions in the board’s terminal.
/claude-code-kanban:show You or Claude Posts a chart, diagram, mockup or explanation of code to a card above the board’s terminal.

The skills need the board server. If the server is not running, a CLI command fails with Cannot reach cck server for <dir> on port <n>. Start the server with claude-code-kanban, then try again.

/claude-code-kanban:kanban [doc|pane|session|task|project|dispatch] <subcommand> [target]

The skill is a thin wrapper over the CLI. The argument is a command and its subcommand, and the current session is the default target. Claude reads the CLI help, one level at a time, before it runs a command, so the help is the reference and the skill needs no change when a command does. With no argument, the skill changes nothing on the board and tells you what the commands can do.

The skill does not move the board while you work. doc link adds a file, or an http(s) URL such as a pull request, to the linked documents of the session. pane add adds a live pane as a tab next to Board, and the board does not switch to it. Only doc preview opens something on your screen: the preview modal. HTML renders in a sandboxed iframe. The server embeds the local stylesheets, scripts and images that the page refers to, such as ./style.css, up to 4 MB for each file and 16 MB in total. Remote URLs load as usual.

To learn what another session did, Claude reads its transcript. session view <id> prints the transcript path, and session search <text> --json prints it for each match.

Example prompts:

/claude-code-kanban:kanban
/claude-code-kanban:kanban session pin --sticky
/claude-code-kanban:kanban doc preview docs/plan.md
/claude-code-kanban:kanban doc link notes/findings.md
/claude-code-kanban:kanban show the active sessions from the last 12 hours

The plugin listens to the board in every session. When you drag one of the session’s task cards to a new column, the session gets a command like this:

[kanban board] Start task <id> "<subject>" now. Mark it completed when done. Description: <description>

The line has no Description: part when the card has no description. Each move sends its own command, so no skill is needed:

Move Command
To in_progress Start task <id> "<subject>" now. Mark it completed when done. The card moves to Completed when Claude finishes.
From in_progress to pending Stop work on task <id> "<subject>" and leave it for later.
To completed Stop work on task <id> "<subject>": it is done.
To cancelled Drop task <id> "<subject>". Keep the changes made so far.
Any other move Task <id> "<subject>" is now <status>.

An idle session starts a turn at once. A busy session gets the prompt when its current turn ends, so a move to Pending does not stop a turn in progress. Moves you make in quick succession arrive as one prompt.

When you send review comments on a file or the plan, the session gets this command, and Claude reads the review file and does what the comments ask:

[kanban board] Address <n> review comments on <source>: <review file>

Know these limits:

  • The session discards moves made before it started listening, for example before a resume.
  • Only your moves and review comments send a prompt. A task you add by hand in the Pending column does not, and neither does Claude’s own TaskUpdate.
  • The queue is in memory and can lose lines. It keeps 50 lines per session at most, and the server cuts each line at 1500 characters. The task file stays the source of truth, so a lost line only means Claude sees the change on its next turn.
  • While the server is down, the session hears nothing. It tries again every 10 seconds and connects when the server starts.

To turn this off, set boardEvents.enabled to false in <config-dir>/.cck/config.json. See Configuration.

/claude-code-kanban:dispatch <task> [--handoff] [--child | --group <name>] [--model haiku|sonnet|opus|fable] [--worktree [name]] [-- <claude args>]

This skill starts other Claude Code sessions through the board. You can type it, and Claude can also start it when you ask it to dispatch or delegate a task. The skill tells Claude to load the dispatch guide first:

Terminal window
claude-code-kanban skills get dispatch

The guide comes with the installed claude-code-kanban package, so it always matches the commands that version accepts. If skills get is an unknown command, the installed version is too old. Update Claude Code Kanban.

By default, Claude asks the started session to reply with SendMessage. Add --handoff when you do not need a reply: Claude passes the task on and moves on, and you follow the session on the board. For bigger tasks the skill picks one of the orchestration patterns. Dispatch needs the embedded terminal. See Dispatch tasks to other sessions for the full flow.

Example prompts:

/claude-code-kanban:dispatch fix the flaky login test in ~/dev/app and message me when it is done -- --permission-mode auto
/claude-code-kanban:dispatch update the changelog in this repo --handoff
Dispatch two sessions in separate worktrees, one for the API and one for the UI, in a group named api-ui, and tell me when both are done.
/claude-code-kanban:show [explain|diagram|chart|mockup] [what to show]

This skill tells Claude how to write a show card: a chart, an SVG diagram, a mockup, or markdown that explains code. The show tool exists only in a session that runs in the board’s embedded terminal. In any other session, Claude does not see the skill. See Show cards for the card and Card kinds for what each kind looks like.

Example prompts:

/claude-code-kanban:show explain the retry path in the uploader
/claude-code-kanban:show chart token use per session today
Show me a diagram of how the request moves through the services.