resolve_ticket ORed the uuid prefix, title and filename predicates into one flat list, so an exact prefix match was reported as ambiguous against any title that merely mentioned that id. Reproduced: `show 641e3d5` on a board where another ticket's title quoted it failed with "Multiple tickets found", and told the user to use the displayed id, which was the id they had just used. The three tiers are now evaluated in order and the first non-empty one wins outright, which is what AGENTS.md always claimed. The ticket also asked for prefix matching to require eight characters, and that is not implemented. The guard it replaced read short_id.len() >= 8 where short_id was always the full uuid, so it was always true and any length already worked. Eight would have regressed that: ls prints seven characters, so the id the tool displays would drop out of the uuid tier and lose to any title quoting it, which is the very bug above. MIN_ID_SEARCH is four, so a short search is still text and `show 641` remains a title search. Docs corrected in four places that all stated the eight character rule: README, AGENTS.md, the opencode tool descriptions and the kanban skill. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
4.0 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(or--due): Due date in YYYY-MM-DD format--owner(or-o): Owner name--priority: Priority level, 1 (most urgent) to 5 (least). Unset if omitted
worklane add -t "Implement login" -d "Add user login page" -t login,auth -p "Design UI" "Build backend" "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 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 comment <ticket> <body>to add notes to tickets