task-runlisted

# Run a task Read [tasks.md](../wiki/references/tasks.md). Tools: `status`, `tasks`, `task`. The task page is the only memory between sessions; keep it true. Progress is prose on the page, written with Edit; the status changes through `task`. Tasks live in a project. This skill runs in the project session, inside the work, where the ordinary file tools reach the code and the documents. ## Start or resume 1. Call `tasks`. Take the task named, else the active one updated last, else the first planned one. Read its page. 2. A task with no Plan section is not ready: hand off to `task-plan`. 3. If the status is planned: with Edit, add a first line under `## Progress` saying what you are starting, then call `task` with `status: active`. Do this before working. 4. If it is active, read the last Progress line first and continue from there. Say what you are picking up. ## Work Follow the plan. If the plan names a skill, run that skill; its procedure governs, and this page records the outcome. The work happens in the project's folder with the ordinary tools. When the work is a repository, read its CLAUDE.md first and commit the way it says; a project's `atlas/` folder is tracked by that repository like any other folder, so a commit may carry the task page's progress with the code. The knowledge base changes only through `plan` and `apply`. Keep a decision the user should be able to find later with the `save` skill. Read the knowledge base when the plan does not answer