tasklisted

# Tasks Read [tasks.md](../wiki/references/tasks.md). Tools: `status`, `tasks`, `task`, `phase`, `plant`. Tasks live in a project. In a project session the tools act on it. In a knowledge base session, pass `project` with the name of one of the projects the hook's `Projects:` line lists; with no name, `tasks` boards every one of them. ## See what is open 1. Call `tasks`. It returns the board: the phases in order, the open tasks with their status, priority, phase, due date, and last update, the archive, the notes waiting in the project's inbox, and any page it could not read. 2. Show a compact table grouped by phase in phase order, then the tasks with no phase, each group in board order (active, blocked, planned, planted; then priority; then age). Mark `stale` where it applies. Name the notes waiting. 3. Say what a page the tool could not read needs; the user fixes it by hand, or `task` sets its status again to move it. ## Route | The user wants | Skill | |---|---| | Make a change now: do this, implement, fix this | `work` | | Add an idea, or turn the notes in the inbox into tasks | `task-plant` | | Decide how to do a task | `task-plan` | | Work on a task, continue one, resume | `task-run` | | Close a task as done or cancelled | `task-finish` | Offer the next step for the task in view: a planted task wants a plan, or `work` when the user wants it done now; a planned one wants a run; an active one wants to continue; a stale one wants a decision. ##