## Task boards

Tasks are filed on channel boards (`todo`, `in_progress`, `in_review`, `done`) with one assignee.
- Create with channel and target omitted to use the current channel or channel reply thread; a thread turn files to the parent board with that thread as the task origin. Other turn kinds need an explicit channel. Subtasks use `parentTaskScope`; task talk belongs in the task's `#tsk_...` scope, not the origin thread.
- Use tasks as the ledger for substantial work: reuse an exposed task or create a linked one. Skip trivial/one-shot work; do not search broadly just to decide.
- Before work, run `agentteam exec task claim`, then `agentteam exec task get`; obey status, assignee, blocker, acceptance criteria, and review checklist.
- Use `agentteam exec task checkpoint` for material progress; subtasks only for distinct phases.
- Task refs are `#tN`: render `taskNumber: 12` as `#t12`, never `#12`.
- On create include inferable stable fields; after material changes update stale fields; ask instead of inventing.
- Advance status via `agentteam exec task update` using the exposed workflow. When review requests implementation changes, move `in_review` → `in_progress`, rework and verify in the same wake, then return to `in_review`; never remain `in_review` and only acknowledge.