Three doc tickets in one commit, since two of them are the same check: run everything the docs claim and see what fails. 8cc254c: the add example in the kanban skill passed -t twice, once where -g for tags was meant, and gave -p three bare positional values instead of three flags. Clap rejected it with exit 2, reproduced verbatim. Rewritten, with a line saying why -t is not tags and why each step needs its own -p, since the example alone does not explain the trap. The "--due (or --due)" filler is gone; --due and --priority have no short form and now say so. a1dbd60: only title is required in the add schema now. The other six fields were unmarked, so the model had to invent a value for every field on every ticket. The other four tool schemas were checked and are already right: ls is fully optional, and the required arguments on show, mv and comment are genuinely required. Every add field was already guarded in execute, so an omitted field adds no flag. 47aa0fe: the README row it describes was already fixed in passing byddbd45e, which rewrote it for the priority work. "ls --status" appears nowhere. What was left was the second criterion, and running every example turned up a different problem: the 141 exit code documented for a truncated pipe only happens when the output exceeds the 64 KiB a pipe holds. A short listing lands in the buffer whole and reports 0. That was my own wording fromb28ddb9and it is now precise. Every example in both files was run against the built binary, with real ids substituted where they use placeholders, and the four documented exit codes were measured rather than assumed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
129 lines
4.1 KiB
Markdown
129 lines
4.1 KiB
Markdown
---
|
|
id: worklane_kanban
|
|
name: worklane_kanban
|
|
version: 1.0.0
|
|
description: >
|
|
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.
|
|
rendering:
|
|
strategy: cli_args
|
|
join_arrays_with: ","
|
|
omit_empty: 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`: 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.
|
|
|
|
```bash
|
|
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.
|
|
|
|
```bash
|
|
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:
|
|
|
|
```bash
|
|
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:
|
|
|
|
```bash
|
|
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
|