A clap value_parser beside priority_level rather than a check inside cmd_add, so a bad date is a usage error with nothing written at all rather than written and then rejected. On set --due as well as add --due, from one definition. The planning skill sets dates through set and never through add, so validating only the command that files a ticket would have left the path the validation exists to protect still accepting "next friday". The shape is checked before chrono sees it. %Y-%m-%d accepts an unpadded 2026-8-9, which would be stored as typed and sort before 2026-10-01. Strict on the way in, tolerant on the way out: util::due_date still cuts a datetime down to its date, since a file written earlier can hold one. PLAN.md told the planner the value was not validated. That is corrected, and the guard test that failed on the edit now pins the half of the warning that is still true: a date cannot be cleared, only replaced. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
9.2 KiB
name: worklane-plan description: Groom a worklane board as a whole rather than one ticket at a time: review whether the priorities are right relative to each other, plan work by setting due dates, check the tags for consistency, and find the tickets that belong together in a campaign. Use for questions about the backlog as a body of work, what to do next week, what is mis-prioritised or mis-tagged, and what could become one goal. Not for filing or working a single ticket.
Planning a worklane board
For "are the backlog priorities right", "plan in tickets for next week", "check the tagging", "which of these could be one campaign". The subject is the board, not a ticket. Filing one, working one and reviewing one are other jobs.
The CLI itself is the worklane skill: the statuses, how a ticket is addressed and
which command owns which field. Read it too. This document is the judgement.
The one rule
Propose the whole set of edits, wait, then apply exactly what was approved.
Every job here writes to many tickets at once, and no field can be cleared back to unset yet, so a date written onto the wrong ticket can only be overwritten, never taken off. A wrong edit to one ticket is a mistake; a wrong sweep is thirty of them with no undo. So a proposal is a list, one line per intended edit, each naming the ticket and the command that would make it:
(1b78a24) priority 3 -> 1 worklane set 1b78a24 --priority 1
(4179958) due -> 2026-08-29 worklane set 4179958 --due 2026-08-29
Then apply what was approved and nothing else. Not "and a few obvious ones while I was there": an approval is for the list that was shown.
Who writes what
Every field has exactly one command that writes it, and a sweep that reaches for any other way is editing the file by hand:
| Field | Writer |
|---|---|
| Priority, Due, Tags | worklane set <ticket> --priority / --due / --tags |
| Relations | worklane relate <ticket> --blocked-by / --regression-of / --relates-to |
| Campaign membership | worklane assign <campaign> <ticket> |
| Owner | worklane chown <user> <ticket> |
| Status | worklane mv <ticket> --status <target> |
Never edit a ticket file directly. The filename, the Status field and the directory
have to agree, and the commands are what keep them agreeing. A hand-written Relations
line is worse still: it is the one section read back by machine, and a target that does
not resolve to a uuid is an error on every later read of that ticket.
The last two rows are in the table to be recognised, not used. See the closing section.
Read the board first
worklane ls # every status, counts then tickets
worklane ls backlog # one status
worklane ls --priority 1 # the top of the pile
worklane show 1b78a24 # one ticket, with its relations and comments
worklane campaign ls # the goals that already exist
ls prints the mark, the id, the title, the owner and the due date. It does not
print tags, and there is no tag filter yet, so any judgement about tags means reading the
tickets themselves. On a board of a few dozen that is a show per ticket and is worth
doing rather than guessing from titles.
Read done too when the question is about what to do next. What was finished last is the
best evidence of what this board actually moves at, and a plan that ignores it is a wish.
Priorities
Priority runs 1 most urgent to 5 least, and may be unset. worklane set <ticket> --priority <n> is the only writer.
Priority is relative. A ticket is never urgent by itself, it is urgent above something else, so every proposed change has to name what it now sits above and below. "This looks important" is not a reason; "this blocks three tickets that are all dated before it" is.
What to look for:
- A blocker priced below what it blocks. Read the Relations. A ticket that others are
blocked bycannot be less urgent than the most urgent of them, or the board is asking for work in an order it will not allow. - A flat board. If almost everything is 3, the field is carrying no information and the answer is not to renumber everything at once. Propose the few that are genuinely 1 and the few that are genuinely 5, and leave the middle alone.
- Too many 1s. If everything is urgent, nothing is. Say how many there are before proposing another.
- A low priority already in
committed. Either the priority is wrong or starting it was, and which one it is decides whether the fix is asetor a conversation. - A priority nobody has touched since the ticket was filed. It is the filer's first guess, not a decision. That is the pile worth reading.
Due dates
worklane set <ticket> --due 2026-08-29, format YYYY-MM-DD.
A value that is not a real calendar date in that exact form is refused before anything
is written, so a typo costs nothing. 2026-8-9 is refused too: the padding is part of
the format. What is still true is that a date, once written, cannot be cleared, only
replaced by another date, so a plan applied to the wrong ticket has no undo.
Ask the system what today is rather than assuming it. A plan built on a guessed date is wrong by however much the guess was wrong.
The rules a dating plan has to keep:
- Nothing is dated before the ticket it is blocked by. Read the Relations first and
date blockers ahead of their dependents. A dependent dated before its blocker is a date
mvwill refuse to honour anyway. - A blocker left undated makes its dependent's date a fiction. Either date both or neither.
- Date what fits, not what exists. Ask how much capacity the week holds, or take the
answer from what
doneshows the board finishing in a comparable stretch. Dating the whole backlog produces a board where every ticket is late, which is the same as no dates at all. - Do not date
done. It is finished; a date on it is noise in every listing. - Leave the rest unset. An unset due date is honest about what has not been planned.
Tags
worklane set <ticket> --tags bug,cli is the writer, and it replaces the whole
field. Restate every tag the ticket should keep, or the ones you left out are gone.
This is the single most destructive thing in this document.
Derive the vocabulary from the board rather than inventing one. Read the tickets, count what is actually used, and show the count before proposing anything. What to report:
- Two spellings of one idea.
bugandbugfix,tuiandui. Pick the one already used more and say so. - A tag used exactly once. Either it is the start of a category and should be applied to its siblings, or it is a private note and should go. Do not leave it as it is without saying which.
- A tag that restates a field. A
p1tag beside a Priority field, anopentag beside a Status, an owner's name as a tag. The field is the writer; the tag is a copy that will disagree with it. This board already made that mistake once with priority and undid it deliberately. - An untagged ticket in a board where everything else is tagged. It is invisible to every question asked by tag.
Tags are for kind, not for state and not for goal. State is the status directory and the fields; a goal is a campaign.
Campaigns
worklane campaign ls
worklane campaign show "v1 release"
worklane campaign add --title "..." --description "..."
worklane assign "v1 release" 1b78a24
A campaign is the tickets that have to be finished together for one outcome. The test is whether you can name the outcome in a single line without listing the members. "The tui is usable on a narrow terminal" is a campaign. "The tui tickets" is a tag.
- Do not group by tag. Ten tickets tagged
bugshare a kind, not a goal, and putting them in a container says nothing that the tag did not already say. - Check what exists first.
campaign lsbefore proposing a new one, or you will propose a second container for a goal that already has one. - A ticket is in at most one campaign, and
assignmoves it rather than adding a second. So two proposed campaigns that overlap are really one proposal to take members out of the other, and it has to say so. - A campaign's state is derived, open until every member is done. There is nothing to close and nothing to move. A campaign whose members are all done is finished already.
assigntakes the campaign first and the ticket second, likechown.
Proposing a campaign means naming the goal, the members, and what is deliberately left out of it. The last part is what makes it a goal rather than a pile.
What a planner does not touch
- Descriptions, acceptance criteria and implementation plans. They are the ticket author's account of the work, and grooming is about how the work is ordered, not what it is. Something wrong in there is a comment on that ticket.
- Status.
mvbelongs to whoever does the work. A plan that moves tickets between columns is reporting progress that did not happen. - Owner.
chownrecords a commitment a person made. Propose it, do not write it, unless you were asked to assign the work. - New tickets. Grooming is about what is on the board. Something genuinely missing is
worth filing, by the rules in the
worklaneskill, but say it is a new ticket rather than folding it into a grooming sweep.