Criteria are stored as - [ ] lines and nothing could tick one, so marking progress meant replacing the whole list through set, losing the state of every other item. check and uncheck are separate commands rather than one verb with a flag, sharing CheckArgs and cmd_check. The criterion is an index first and a substring second, so a criterion whose text is literally "2" is reachable only by substring. A number out of range is reported as a bad index rather than as a substring that missed. Only the character between the brackets is spliced, so the text keeps whatever indentation and spacing it had. Criteria are counted inside the Acceptance Criteria section only, so a checkbox written into a description is not a criterion and a handwritten line in the section takes no number. With the criterion omitted, the criteria are listed and the number asked for when stdin is a terminal. Where it is not, the same list comes back as an error instead. Prompting regardless would leave the opencode wrapper blocked on a stdin that never closes, and that is the choice resolve_ticket already makes for an ambiguous match, for the same reason: the wrapper keeps stderr and throws on the code, so a list printed to stdout would be discarded. Any listing of a subset keeps the real numbers. Renumbering the matches from one would contradict the advice to use the number and point at the wrong criterion. show now numbers the criteria as "1. [x] text", so the index is visible where the ticket is read. That also drops a manual prefix strip, so clippy is one warning below where it started. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
6.3 KiB
id, name, version, description, rendering
| id | name | version | description | rendering | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| worklane_kanban | worklane_kanban | 1.0.0 | Creates Kanban-style tickets in Worklane using the `worklane add` CLI command. Supports listing tickets with `worklane ls`. Both commands support title, description, acceptance criteria, implementation plan, tags, due date, owner assignment, and status filtering. |
|
Worklane Kanban Skill
Use this skill when creating, listing, or managing Kanban-style tickets via the worklane CLI.
When asked to "create a ticket", use the worklane add command.
When using backticks in the command arguments, escape them so the terminal doesn't execute them.
When asked to "implement", "work on" or "read" a ticket, use the worklane show command.
Commands
worklane add
Add a new ticket to the backlog.
Required:
--title(or-t): Ticket title
Optional:
--description(or-d): Ticket description--acceptance(or-a): Acceptance criteria (repeat flag for each criterium)--plan(or-p): Implementation plan steps (repeat flag for each step)--tags(or-g): Tags (comma-separated)--due: Due date in YYYY-MM-DD format. No short form--owner(or-o): Owner name--priority: Priority level, 1 (most urgent) to 5 (least). Unset if omitted. No short form
Tags are -g, not -t: -t is the title, and passing it twice is an error. Each
plan step needs its own -p, since a bare value after one is not a second step.
worklane add -t "Implement login" -d "Add user login page" -g login,auth -p "Design UI" -p "Build backend" -p "Write tests" --due 2026-06-01 --owner "ilya"
When there's multiple acceptance criteria, add each using a separate --acceptance or -a flag.
When there's mulitple steps to the implementation plan, add each using a separate --plan or -p flag.
worklane add -t "Implement logic" -a "Acceptance criterium 1" -a "Acceptance criterium 2" -p "Step 1" -p "Step 2"
worklane ls
List tickets, optionally filtered by status.
Valid statuses: backlog, committed, reviewing, done
worklane ls # List all tickets
worklane ls backlog # List tickets in backlog
worklane ls done # List completed tickets
worklane ls --priority 1 # Only the most urgent, any status
worklane ls backlog --priority 2 # Composes with the status filter
Tickets are listed priority first, then by title. Tickets with no priority sort last.
worklane show
Show the full details of a single ticket by UUID or title.
worklane show "ticket title or uuid"
worklane mv
Move a ticket between statuses.
Positional arguments:
<id>: Ticket UUID prefix (4+ characters) or title
Required options:
--status <target>: Target status (backlog,committed,reviewing,done)
Options:
-f: Force move (allows skipping stages and backward moves)
Default behavior: Only allows forward moves, one stage at a time (backlog -> committed -> reviewing -> done).
Examples:
worklane mv ticket-id --status committed # Move forward one stage
worklane mv ticket-title --status reviewing -f # Force skip stages
worklane mv a1b2c3d4 --status committed # Move by UUID prefix
worklane mv "My Ticket" --status done -f # Move by title with force
worklane set
Replace fields on an existing ticket. Only the fields given are touched; ticked criteria and handwritten sections are left alone. At least one field is required.
Positional arguments:
<ticket>: Ticket UUID prefix (4+ characters) or title
Options: --title, --description (or -d), --acceptance (or -a), --plan
(or -p), --tags (or -g), --due, --priority
Owner is not settable here, and neither is status: mv owns status. Changing the
title renames the file, keeping the UUID.
worklane set a1b2c3d4 --priority 1
worklane set a1b2c3d4 --title "A clearer title" --due 2026-12-31
worklane set a1b2c3d4 -a "First criterium" -a "Second criterium"
worklane append
Add to a section without replacing what is there. The description gains a new paragraph; criteria and steps go on the end of their lists, steps numbered on from the last. At least one section is required.
Positional arguments:
<ticket>: Ticket UUID prefix (4+ characters) or title
Options: --description (or -d), --acceptance (or -a), --plan (or -p)
worklane append a1b2c3d4 -d "A paragraph amending the description."
worklane append a1b2c3d4 -a "One more criterium"
worklane append a1b2c3d4 -p "A later step"
worklane check and worklane uncheck
Tick or untick a single acceptance criterion. Every other criterion keeps its state, and handwritten lines in the section are left alone.
Positional arguments:
<ticket>: Ticket UUID prefix (4+ characters) or title[criterion]: The number as shown byworklane show, or a substring of its text
Omit the criterion and the numbered criteria are listed and the number asked for. With no terminal, as when driving the CLI from a tool, the same list comes back as an error instead, so re-run with the number. A substring matching more than one criterion is an error listing the matches with their real numbers.
worklane check a1b2c3d4 2
worklane check a1b2c3d4 "renames the file"
worklane uncheck a1b2c3d4 2
worklane comment
Add a comment to a ticket.
Positional arguments:
<ticket>: Ticket UUID prefix (4+ characters) or title<body>: Comment text
Comments are stored as timestamped markdown files in .worklane/comments/<ticket-uuid>/ and include the git author and timestamp.
Examples:
worklane comment ticket-id "Reviewed, looks good"
worklane comment "My Ticket" "Needs changes to the UI"
worklane comment a1b2c3d4 "LGTM, approved"
Workflow
- Use
worklane addto create tickets with all relevant details - Use
worklane ls [status]to view tickets by status - Use
worklane show <id>to view full ticket details - Use
worklane mv <id> --status <target>to move tickets through the workflow - Use
worklane set <ticket>to correct a field, orworklane append <ticket>to add to a section - Use
worklane check <ticket> <n>to tick a criterion as it is met - Use
worklane comment <ticket> <body>to add notes to tickets