(8c8a520) Ship a board administration skill, and bump to 0.26.1
Three skills taught the CLI, the review and the grooming sweep. Nothing taught the board itself, and two jobs fell in the gap: deciding what the tags are, now that `tags add` and `tags set` exist to declare them, and putting a board back together when its files and fields disagree. `worklane-admin` is the fourth. It is the one asset written to hold for a board that tracks no software, since a vocabulary skill built around `bug` and `cli` teaches nothing to a board tracking a household, so its worked examples span a tool, a product strategy and a house. Tags as axes rather than as a pile of words, what an annotation has to say to stop drift, which is the boundary against the neighbouring tag and not the definition, and the fact that renaming a tag means rewriting the Tags field of every ticket carrying it. The repairs are by symptom and every one was run against a scratch board rather than reasoned from the source, which is what the ticket demanded and what turned up the one that matters: a ticket whose file sits in `done` while its Status field says `backlog` cannot be repaired by one `mv`, because `mv` reads the current status from the directory and refuses the target it is already in. Two moves fix it. That is 7f772a7. Verifying also turned up that nothing removes a relation, 8556048. The line against `worklane-plan` is drawn in both documents: this one decides the vocabulary, that one applies it across tickets. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
239d951b8c
commit
8e2ab6332c
@@ -13,6 +13,7 @@
|
||||
- `assets/SKILL.md` - the agent skill for the CLI itself, embedded with `include_str!`
|
||||
- `assets/REVIEW.md` - the agent skill for reviewing a finished ticket, shipped the same way. Assets are named after the role they teach; `SKILL.md` keeps its name because the role it teaches is the CLI
|
||||
- `assets/PLAN.md` - the agent skill for grooming the whole board: priorities, due dates, tags and campaigns
|
||||
- `assets/ADMIN.md` - the agent skill for the board itself: designing and annotating the tag vocabulary, and repairing a board whose files and fields have come apart. The one asset written to hold for a board that tracks no software, so its examples span three subjects on purpose. It draws the line against `PLAN.md` in both directions: this one decides the vocabulary, that one applies it
|
||||
- `assets/TOOL.ts` - the opencode tool definitions wrapping the CLI, embedded the same way and installed by `install-tool`. The only asset that is not a document and the only one that reaches a single agent
|
||||
- `tests/` - Integration tests using `assert_cmd` and `assert_fs`, one file per command
|
||||
- Unit tests live beside the code in `#[cfg(test)] mod tests`, in `util.rs`, `handlers.rs` and `tui.rs`
|
||||
|
||||
Reference in New Issue
Block a user