diff --git a/.opencode/skill/worklane-kanban-skill/SKILL.md b/.opencode/skill/worklane-kanban-skill/SKILL.md index f5b757c..c7b4290 100644 --- a/.opencode/skill/worklane-kanban-skill/SKILL.md +++ b/.opencode/skill/worklane-kanban-skill/SKILL.md @@ -176,12 +176,29 @@ worklane comment "My Ticket" "Needs changes to the UI" worklane comment a1b2c3d4 "LGTM, approved" ``` -## Workflow +## Working a ticket -1. Use `worklane add` to create tickets with all relevant details -2. Use `worklane ls [status]` to view tickets by status -3. Use `worklane show ` to view full ticket details -4. Use `worklane mv --status ` to move tickets through the workflow -5. Use `worklane set ` to correct a field, or `worklane append ` to add to a section -6. Use `worklane check ` to tick a criterion as it is met -7. Use `worklane comment ` to add notes to tickets +Move the ticket as you work it, not afterwards. The board should say what is happening +now, not only what already landed. + +1. `worklane show ` to read it +2. **`worklane mv --status committed` before writing any code.** This is what marks + the ticket as being worked on, so it belongs at the start +3. Do the work. `worklane check ` as each criterion is met +4. `worklane comment ` with anything worth recording: a decision, a rejected + acceptance criterion, something the ticket got wrong +5. **`worklane mv --status reviewing` once it is done and the tests pass** + +Only one stage forward is allowed at a time, so a ticket left in `backlog` until the end +cannot go straight to `reviewing`. It has to be walked through `committed` anyway, which +makes moving it up front the same two commands in a more useful order. + +## Commands + +- `worklane add` creates tickets with all relevant details +- `worklane ls [status]` views tickets by status +- `worklane show ` views full ticket details +- `worklane mv --status ` moves tickets through the workflow +- `worklane set ` corrects a field, `worklane append ` adds to a section +- `worklane check ` ticks a criterion as it is met +- `worklane comment ` adds notes to tickets diff --git a/AGENTS.md b/AGENTS.md index ec0ee4b..187f1fb 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -20,6 +20,15 @@ ## Status Workflow `backlog` → `committed` → `reviewing` → `done` +**Move the ticket as you work it, not afterwards.** `mv --status committed` before +writing any code, and `mv --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