threadlisted

# Threads Read [threads.md](../wiki/references/threads.md). Tools: `status`, `threads`, `thread`, `phase`. A thread is one line of work. It moves stub, spec, plan, receipt, and each stage is a document the user can open. In a knowledge base session pass `project`; with no name, `threads` lists every project that uses it. ## Show the board Call `threads`. Show the open threads under their stage, plan 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. ## Route | The thread needs | Skill | |---|---| | To exist: an idea, a bug, a chore, a note in the inbox | `thread-stub` | | A definition: what done means | `thread-spec` | | An approach | `thread-plan` | | The work, or the next step of it | `thread-run` | | An end: completed or killed | `thread-receipt` | | All of it now, from one sentence | `work` | Offer the next stage for the thread in view. Size the ceremony to the thread: a small one skips the spec, and a trivial one goes from stub to receipt. Say which stages you skip and why. ## Quick moves 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