# Create and manage tasks

Tasks turn a broad intention into work with a visible state. Use Projects and task lists to group them, then define what each task must accomplish.

## Create a task
Open **Tasks** and create a task. Fill in a clear title and description. Set priority, assignee, due date, and tags when useful. Choose its project and task list so it appears in the right context.

## Define completion
Add **Exit criteria** for the conditions that must be true before completion. Add an **Action plan** for the ordered steps. Use **Agent instructions** for execution guidance; it is different from evidence that the work was done.

## Add dependencies
Use **Depends on** to identify prerequisite tasks. The editor refuses choices that create a dependency cycle. A task can be blocked while prerequisites are unfinished and become available after they reach a terminal state. A cancelled prerequisite is terminal, so check whether its cancellation also changed the dependent task’s scope.

## Follow and discuss work
Open task details to review description, exit criteria, plan, research notes, execution notes, and comments. Post a comment when a decision changes. Update the state only to reflect actual progress.

## Finish honestly
Gideon refuses completion when declared exit criteria remain unfinished. Resolve the criteria or correct the scope with an explicit explanation; do not remove a valid criterion merely to make a status turn green.

> **Try this**
> Create tasks for [outcome] under [project]. Give each one an observable exit criterion and identify dependencies. Show me the proposed list before starting execution.