Ansho ReiandClaude Opus 5 a16169ce8c (b8ce18c) Show a blocked marker on the tui card, and bump to 0.13.4
A ticket held up by an open blocker looked exactly like one that is ready,
and the board is where the next thing to pick up is chosen.

The mark is × in brightred, after the short id. Not a fourth Geometric
Shapes glyph: those are the priority meter's, two cells away, and another
circle there reads as part of that ramp. × is Latin-1, like the middle dot
the unset priority draws, so it renders wherever the meter does.

After the id rather than before it, because ahead of it the mark would push
every id in the column out of line whenever one card was blocked. It is
measured before the project label and the due date, so both give way to it:
those are context for a ticket somebody can start, and this is the one thing
on a card that says not to. Dropped whole when the row cannot hold the
identity and the mark together.

No scan of the board per tick was needed after all. collect_ticket_items
also reads the ticket's own uuid and the targets of its blocked by lines,
off the file it is already holding, and mark_blocked walks the four columns
once for a uuid-to-status map and once to answer every card. The flag is on
Card rather than TicketItem: the answer is about two tickets at once, so no
card can reach it alone, and it is settled at reload the way project is.

The merge carries each card's flag from the board it came from. relate
resolves its target inside one .worklane, so a blocker in another project is
not a relation anything can record, and recomputing over the merged columns
would let one project's uuid match another project's ticket.

project_label now takes the width the row has actually spent, measured off
the spans, instead of adding up the widths those spans are supposed to have.
The hand-written sum left out the space after the priority mark, so a cut
label was handed one cell more than the column had.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-22 13:02:13 +02:00
2026-05-14 20:41:40 +02:00

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, 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>
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.

S
Description
No description provided
Readme
3.7 MiB
Languages
Rust 97.8%
TypeScript 1.9%
Makefile 0.3%