Nothing could change a ticket after it was created. mv wrote status, comment appended a file, and that was the whole set of mutations, so correcting a typo or adding a criterion meant hand editing the markdown. Two commands rather than the one vague "edit" the ticket described. set replaces a field, append adds to a section, so the verb carries the meaning instead of a prefix on seven flag names, and append only offers the three sections that hold multiple lines. Owner is absent from both, it belongs to the chown command filed alongside this, and status stays mv's. One field, one writer. Sections are a table, DESCRIPTION, ACCEPTANCE and PLAN, each carrying a heading, a label, the placeholder add writes when empty, and a kind. Both commands walk it, so a section added later is one entry rather than edits in two places. Everything is targeted line surgery and never a regenerated file, which is what keeps a ticked criterion ticked and a handwritten section intact when an unrelated field changes. Appending to a numbered section continues from the count already there rather than renumbering above it, so a handwritten line survives exactly as written. Appending to an empty section replaces the placeholder instead of following it. An empty value is a paragraph break for a section and a usage error for a scalar, since it looks like a way to clear a field and clearing is not supported yet. No-op detection compares the whole file before and after each edit, so a field set to the value it already holds is reported unchanged and nothing is written. Two things came out of building it. move_ticket_file's staged write is extracted as write_then_replace, now the only way any ticket file is written. And the file is located by uuid rather than by title: titles are not unique, add allows duplicates on purpose, and the old title scan meant mv <uuid-of-second> moved the first ticket sharing its title. Reproduced, fixed, and pinned by a test. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
167 lines
5.5 KiB
Markdown
167 lines
5.5 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 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.
|
|
|
|
```bash
|
|
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`)
|
|
|
|
```bash
|
|
worklane append a1b2c3d4 -d "A paragraph amending the description."
|
|
worklane append a1b2c3d4 -a "One more criterium"
|
|
worklane append a1b2c3d4 -p "A later step"
|
|
```
|
|
|
|
### `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 set <ticket>` to correct a field, or `worklane append <ticket>` to add to a section
|
|
6. Use `worklane comment <ticket> <body>` to add notes to tickets
|