Files
worklane/.opencode/skill/worklane-kanban-skill/SKILL.md
T
Ansho ReiandClaude Opus 5 ddbd45e332 (dca0b61) Add priority as a ticket field
Priority lived in tags, as p1 to p3, which ls could neither sort nor
filter on, nothing validated, and a typo like P1 passed silently. ls
sorted by title only, so a backlog of any size gave no ordering signal.

Levels are 1 to 5 with 1 most urgent, matching what the tags meant.
Omitting the flag leaves the field _Not set_, like Due and Owner: there is
no implicit middle level, because a priority nobody chose is worse than
none. clap rejects anything outside the range before a ticket is written.

Priority parses to three states rather than two. A stored value outside
the range is Invalid, kept distinct from Unset, so a typo cannot read as
"no priority": it shows as ? and sorts just ahead of the unset tail.

ls sorts on priority and falls back to the old title sort, and --priority
filters, composing with the status filter in both the grouped and the
filtered listing. TicketItem becomes a struct, since a sixth tuple field
was past reading.

Migrated the 31 tickets already carrying p1 to p3 tags: the level moves to
the field and the tag is dropped.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-20 15:36:19 +02:00

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.
strategy join_arrays_with omit_empty
cli_args , true

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 (8+ 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 (8+ 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

  1. Use worklane add to create tickets with all relevant details
  2. Use worklane ls [status] to view tickets by status
  3. Use worklane show <id> to view full ticket details
  4. Use worklane mv <id> --status <target> to move tickets through the workflow
  5. Use worklane comment <ticket> <body> to add notes to tickets