Say when to move a ticket, not just how
Both AGENTS.md and the kanban skill listed the statuses and the mv command without ever saying at what point to run it, so a ticket could sit in backlog until the work was finished and the board said nothing while it was in progress. That is what happened to f6af387. The rule is now in both places, and in both for a reason: the skill is what an agent loads to work tickets in any repo, and AGENTS.md is what an agent working on worklane itself reads, possibly without ever loading the skill. The skill's Workflow section also becomes a sequence for working one ticket rather than an unordered list of commands, with the command list kept separately. Worth stating because it is self-enforcing: only one stage forward is allowed at a time, so a ticket left in backlog cannot go straight to reviewing and has to be walked through committed regardless. Moving it up front is the same two commands in a more useful order. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
78831f1a39
commit
77bf2d9e2a
@@ -20,6 +20,15 @@
|
||||
## Status Workflow
|
||||
`backlog` → `committed` → `reviewing` → `done`
|
||||
|
||||
**Move the ticket as you work it, not afterwards.** `mv <id> --status committed` before
|
||||
writing any code, and `mv <id> --status reviewing` once it is done and the tests pass.
|
||||
The board is then true while the work is in progress, not only after it lands, which is
|
||||
the whole point of having a `committed` column.
|
||||
|
||||
Only one stage at a time is allowed, so a ticket left in `backlog` until the end cannot
|
||||
go straight to `reviewing` and has to be walked through `committed` anyway. Doing it up
|
||||
front is the same two commands in a more useful order.
|
||||
|
||||
## Testing
|
||||
- Run: `cargo test`
|
||||
- Tests use `assert_cmd` and `assert_fs` for CLI testing
|
||||
|
||||
Reference in New Issue
Block a user