# Tasks: keep a job together

A Forge task is the home for one piece of work. It keeps the request, its steps, updates and supporting material together, so the next person or agent can see what has happened without rebuilding the story from chat messages.

## Start with a useful outcome

Give the task a plain title that says what needs to be true when it is finished. Add a short description with the context someone needs to begin. Then add steps for work that can be checked separately.

For example, a task called **Prepare the site visit** might have steps to confirm access, collect drawings and record the visit outcome.

## Work from the task

Open **Workspace → Tasks** and select a task to read its description, steps and activity. Keep updates with the task when they change the work or explain a decision. Mark a step done only when its stated result is available.

An agent can read, create and update work through `manage_task`. Tell it the workspace and the task you mean; ask it to read the task before changing it when the current state matters.

## A prompt to try

```
Read the task “Prepare the site visit” in this workspace. Summarise its goal, open steps and anything blocking progress. Do not change it.
```

```
Create a task for preparing the site visit. Add separate steps for access, drawings and the visit outcome. Show me the draft before making any irreversible change.
```

## Keep it reliable

Use the task as the source of the current plan. Put a date, tag or assignee on the task when it helps people find or own the work. Put reusable facts in workspace knowledge when they should outlive this one task.

See [Organise work with tags and ownership](/help/organising-work) and [Dates and recurring work](/help/dates-and-recurring-work).