# Tasks

`@arbe/task` is repo-native planning system — local on purpose. Lives in `.arbe/tasks/` as `meta.json` + `deps.json` + one JSON file per task. We use it primarily to build arbe. Code is in `packages/task`.

Work with tasks using the `arbe task` CLI, or edit the JSON files directly. 

`arbe task list` shows tasks by status. 
`arbe task ready` shows `open` and `in_progress` tasks with no open `blocks` deps

It can be useful to combine the `--json` flag with `jq`. Else check `--help` for tips.

A task body describes the goal, it's not meant for 10-page design docs. Keep it to one screen — Why, outcome, scope. Linking and referencing ./docs is helpful. When a task body grows too large, ask why and whether we want to split into multiple tasks, epics or docs.

```
status   open · in_progress · blocked · closed · deferred
type     bug · feature · task · chore · epic
priority 0..4 (critical, high, medium, low, backlog)
deps     blocks · discovered-from
```