# Worklane Worklane is a local Kanban flow for agentic software development. ## Commands | Command | Description | |---------|-------------| | `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 | | `worklane ls [status]` | Lists tickets, sorted by priority then title. Optional positional status, and `--priority <1-5>` | | `worklane show ` | Shows ticket by UUID prefix (4+ chars), title substring, or filename substring | | `worklane mv --status [-f]` | Moves ticket between statuses. Default: forward only, one stage at a time. `-f` bypasses both restrictions | | `worklane comment ` | Adds a comment to a ticket by UUID or title | ## 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.