Tasks and reviews

Tasks are the planning objects that connect project intent to ACP execution. A task can have comments, dependencies, releases, sprints, multiple linked threads, and a review loop that keeps implementation and approval visible.

Tasks and reviews

Turn project work into repeatable task threads, review loops, comments, and status transitions.

What tasks are

Tasks are ACP’s structured unit of planned work. They hold title, description, priority, status, assignee, dependencies, comments, review settings, and the threads that have run against the work.

Use tasks when work needs a durable planning object instead of a one-off prompt.

Attach multiple implementation or review threads to the same task over time.

Keep comments, status, dependencies, and execution history together.

How tasks start threads

A task can start more than one thread. That supports implementation passes, review passes, requested changes, and follow-up work without losing the relationship to the original ticket.

Use start-thread when your app wants to create a thread and stream it separately.

Use run-thread when you want ACP to create and execute the task thread synchronously.

Use linked thread IDs as the task’s execution history.

How reviews fit in

Review flows are modeled on top of the same task and thread primitives. A reviewer can approve, request changes, or start another review thread, while all feedback stays attached to the task and its thread history.

Use in_review and done to separate implementation completion from final acceptance.

Request changes by adding a task comment and starting another task-linked thread.

Use task dependencies so finished upstream work no longer blocks downstream tasks.