thread-worklisted

# Work a thread The conductor of the thread stages. Given a thread, it reads where the thread stands and runs the next stage's skill; given a sentence, it opens the thread first. It goes on through the stages while the user agrees, and it holds no stage procedure of its own: each stage is done as its skill says. Tools: `status`, `threads`, `thread`. Reads [threads.md](../thread/references/threads.md). ## 1. Find the thread 1. Call `status` and `threads`. 2. A thread named by id or title, or one the user plainly means: take it. In a hub, a member's thread is worked in the member's own session: say so and offer `atlas-obsidian open-agent <project> --thread <id>`, because the code is there. 3. A sentence that matches no open thread is new work: open it with `thread-stub`'s rule, the user's words verbatim, and say so. 4. The change belongs to another project the atlas lists: say so and offer the same command for that project. ## 2. Size the ceremony Decide which stages the change needs, and say so in one line before the first: | The change | Stages | |---|---| | Its definition of done is in doubt, or it spans sessions | spec, plan, run, receipt | | Clear, and more than a few edits | plan, run, receipt | | One obvious edit | run, receipt, with a plan of a few lines | | Not worth doing | receipt, killed | A skipped stage may be filed later. The user can always ask for more ceremony; offer less only when the change is plainly small. ## 3. Run the next stage