thread-runlisted

# Run a thread Read [threads.md](../wiki/references/threads.md). Tools: `threads`, `thread`. The work happens in the work folder, the parent of `atlas/`, with the ordinary tools. The plan document is the memory between sessions: keep it true. ## Start or resume Call `threads`. Take the thread named, else the one with a plan that was updated last. Read its spec and its plan, and the last lines under `## Progress`. Say what you are picking up. A thread with no plan goes to `thread-plan`, unless the work is small enough to need none: then file a plan of a few lines and go on. ## How to work - **Own the outcome.** The spec is the intent and the plan is the approach; neither is a cage. When the work shows a better way to reach the intent, in the code, the interface, or the look and feel, take it, and record the change under Progress. When the intent itself should change, stop and ask. - **Slices and commits.** Work in the slices the plan names. Commit each one when it works, the way the work's CLAUDE.md says. `atlas/<name>/` is tracked like any other folder, so a commit may carry the plan's progress with the code. Use a branch when the repository's habits call for one. - **Tests.** Behavior that can break gets a test, written with the code or before it. Match the project's own standard; do not test what cannot fail. Run the tests before every commit. A thread closes only when they pass. - **Subagents.** Use them where the work splits into independent slices