5ae9c7fe00856872d2703e1d63dfc640b599a95d
A column of ▁▄▆█ read as undifferentiated blocks. What is worth seeing at a glance is which kind of edge a row is: × for blocked by and blocks, → for relates to, ← for regression of and regressed by. The labels are five long words that blur when one ticket carries several, and the rows holding it up are now the crosses. Both directions of a kind carry one mark, since blocked by and blocks are the same edge read from two ends and the label is what says which end you are on. × is BLOCKED_MARK, the constant a held-up card already draws, in the same brightred. On a card it says this ticket is held up, in the block that this edge is what holds one, which is one word, so one glyph and one definition: the constant moved to util.rs, where both renderers can reach it. Brightred rather than the red asked for, because the id one cell to the right is red and the two would have blended. The arrows are the ones the footer already draws, so they render wherever it does, and no_relation_mark_is_a_priority_glyph pins all three against every level of the meter: the circles belong to priority. The mark now survives a target the board cannot find, because a kind is read from the ticket's own file rather than from the board. Only the name is gone, and `_missing_` in grey is what says so. That is one case fewer than the status mark had, which needed a `?` for a target with no status to show. What this gives up is the status: 6ce2c47's motivation was reading whether a blocker is finished without leaving the overlay, and nothing in the block shows that now. Its criteria 1 and 3 describe the commit before this one, and the ticket says so. RelationTarget went with it. Nothing read the status field once the mark stopped keying on it, and a field written but never shown is a field that goes stale unnoticed, so RelationRow carries the kind and the title and the status is one lookup away on the index if a later ticket wants it. A patch, not a second minor: 0.15.0 was the arrival of a mark and settling which glyph it is belongs to that, where a second minor would read as two features. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Worklane
Worklane is a local Kanban flow for agentic software development.
Commands
| Command | Description |
|---|---|
worklane or worklane tui [path...] |
Opens the board: four status columns, redrawn when the tree changes. Read only. Opens on backlog, committed and reviewing; d shows or hides done, whose count stays in the footer either way. Arrows or hjkl to move, enter for detail, pgup/pgdn to scroll an open ticket, / to jump to the first ticket whose id or title matches, y to copy the selected ticket's short id to the clipboard, q to quit. Each path opens the first .worklane at or above it, the working directory by default. Several paths are monitored together, as a tab per project plus an all tab that merges them, with tab and shift+tab between them |
worklane init |
Creates .worklane/ with backlog, committed, reviewing, done directories |
worklane add |
Creates a ticket in backlog with --title, --description, --acceptance, --plan, --tags, --due, --owner, --priority flags. --due takes YYYY-MM-DD and refuses anything else at parse time |
worklane ls [status] |
Lists tickets, sorted by priority then title. Optional positional status, and --priority <1-5>, --tag <tag> and --campaign <campaign>, which compose in any combination. --tag matches a whole value of the comma-separated Tags field, case sensitively, so --tag bug does not list a ticket tagged bugfix or one tagged Bug |
worklane show <id> |
Shows ticket by UUID prefix (4+ chars), title substring, or filename substring |
worklane mv <id> --status <target> [-f] |
Moves ticket between statuses. Default: forward only, one stage at a time. -f bypasses both restrictions |
worklane set <ticket> |
Replaces fields with --title, --description, --acceptance, --plan, --tags, --due, --priority. At least one required. Changing the title renames the file, keeping the UUID |
worklane append <ticket> |
Adds to a section with --description, --acceptance, --plan. At least one required. The description gains a paragraph; list items go on the end, steps numbered on from the last |
worklane relate <ticket> |
Records an edge to another ticket with --blocked-by, --regression-of or --relates-to, each repeatable. At least one required. Only the ticket named is written; show derives the other end by scanning. mv refuses to move a ticket blocked by one that is not done, unless -f |
worklane chown <user> <ticket> |
Sets the Owner field, the only command that writes it. Free text, checked against nothing. User first and ticket second, after Unix chown |
worklane check <ticket> [criterion] |
Ticks one acceptance criterion, by number as shown by show or by a substring. Prompts with the numbered list if omitted, or errors with it when there is no terminal |
worklane uncheck <ticket> [criterion] |
Unticks one acceptance criterion, addressed the same way |
worklane comment <ticket> <body> |
Adds a comment to a ticket by UUID or title |
worklane install-skill [skill] |
Writes the embedded agent skills to ~/.claude/skills/<skill>/SKILL.md, which Claude Code and opencode both read. Three ship: worklane teaches the CLI, worklane-review reviews a finished ticket against the code that claims to close it, worklane-plan grooms the board as a whole, its priorities, due dates, tags and campaigns. Every document unless one is named. Leaves a modified copy alone unless --force; --print writes one to stdout instead and needs the name |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | An error, such as no matching ticket or an ambiguous search |
| 2 | A usage mistake, such as an unknown flag |
| 141 | Output was piped to a reader that stopped early, for example worklane ls | head -3 |
141 is 128 + 13, the shell's way of reporting death by SIGPIPE. Worklane restores
the default signal disposition so a truncated pipe is quiet, the way head and
sort are, rather than printing a panic. A script using set -o pipefail will see
141 for a case that is not a failure, so guard for it there.
Whether a truncated pipe reports 141 or 0 depends on the size of the output, not on the command. A pipe holds 64 KiB, so a listing that fits lands in the buffer whole and the writer never learns the reader left, giving 0. Only output past that gets far enough to be cut off. Either way nothing is printed to stderr.
Languages
Rust
97.8%
TypeScript
1.9%
Makefile
0.3%