claude-code-kanban 7.6.1 → 7.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: kanban
3
3
  description: Kanban board CLI — show the user a file or page, link a doc or PR, add a pane, open or pin a session, find a session's transcript, list tasks.
4
- argument-hint: '[doc|pane|session|task|project|dispatch] <subcommand> [target]'
4
+ argument-hint: '[doc|pane|session|task|project|dispatch|terminal] <subcommand> [target]'
5
5
  ---
6
6
 
7
7
  # Kanban Skill
@@ -16,10 +16,12 @@ This session id is `${CLAUDE_SESSION_ID}`. `--session` defaults to it through `$
16
16
  |---|---|
17
17
  | `doc` | `link`, `unlink` a file or URL to the session · `list` its links · `preview` a file in a modal |
18
18
  | `pane` | `add` a URL or a local file as a background tab · `rm` · `list` |
19
- | `session` | `list` · `search <text>` · `open <id>` focuses it · `view <id>` stats and transcript path · `plan <id>` · `agents <id>` · `pin <id>` |
19
+ | `session` | `list` · `search <text>` · `open <id>` focuses it · `view <id>` stats and transcript path · `plan <id>` · `agents <id>` · `pin <id>` · `group <id> <group>`, `ungroup <id>` in the sidebar |
20
+ | `group` | `list` the sidebar groups, by name and id · `create <name>` · `rename <group> <name>` · `rm <group>` · `prune` the empty ones |
20
21
  | `task` | `list` for a session, a project or the whole board |
21
22
  | `project` | `list` |
22
23
  | `dispatch` | `start`, `list`, `end` — run `/claude-code-kanban:dispatch` instead |
24
+ | `terminal` | `list` every terminal in cck, read-only |
23
25
 
24
26
  ## Run a command
25
27
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: show
3
- description: Show card guide for the cck overlay. Use before a show call that posts HTML (a chart, mockup or diagram), a mermaid diagram, or explains code (a call stack or tree).
3
+ description: Show card guide for the cck overlay. Cards can be a table, chart, diagram, mermaid, mockup, call stack, code tree, diff, widget, or buttons and forms that take the user's answer.
4
4
  argument-hint: '[explain|diagram|chart|mockup] [what to show]'
5
5
  ---
6
6
 
@@ -18,6 +18,10 @@ This applies to the `.html` file that a `kind: "html"` post names.
18
18
  - The card is about 360 to 640 px wide and sizes its height to the content. Keep the content in normal flow, without `position: fixed` or `100vh`.
19
19
  - One chart or diagram per card, under an `<h2>` that says what to see. Keep it flat: solid fills and 1 px lines.
20
20
  - Open links with `<a href="https://...">`; the overlay opens them in a new browser tab.
21
+ - To ask the user something, let the card answer for them. You get the answer as your next prompt, with a file that holds the fields as JSON.
22
+ - One choice: a button per answer, sent on click: `<button data-cck-action="approve">Approve</button>`.
23
+ - Several inputs: one form, sent once on submit with every field: `<form data-cck-submit="plan">…<button>Send</button></form>`. Give each input a `name`. `required` works.
24
+ - Action names use letters, digits, `.`, `_` and `-`. The button text is the label you get. Nothing else in the card sends.
21
25
  - Take every color and font from these variables, so the card follows the user's light or dark theme:
22
26
 
23
27
  | Variable | Use |