threadlisted

# The threads A thread is one line of work in a project: a feature, a bug, a chore. It moves stub, spec, plan, receipt, and each stage is a document the user can open under `threads/`. This skill is the home of that half: the board, the quick changes to a card, the phases, and a review of the whole board. Moving a thread to its next stage is `thread-work`'s. Tools: `status`, `threads`, `thread`, `phase`. Reads [threads.md](references/threads.md). This session's project is implied; `project` reaches another one the atlas lists. In a project with members, a thread named by id or title may be a member's: the tool makes the change in the project that owns it. Say which project took the change. ## Show the board Call `threads`. Show the open threads under their stage, the furthest stage first, with priority, phase, last update, and `blocked` or `stale` where it applies. Name the notes that wait in the inbox and any page the tool could not read, with what the page needs. Give the path of `threads/threads.md`: it is the same board in Obsidian. For one thread, call `threads` with `id` and read the documents it lists. ## Change a card Priority, phase, title, block, unblock: one `thread` call with `id` and the field. `blocked` holds what the thread waits on, in one line; `""` unblocks. Never close a thread here: a receipt needs its text and its checks, and `thread-receipt` writes it. ## Phases `phase` with `action: create` (`title`, `goal`, optional `order`), `rename` (`title