4. Create a task

Tasks → New task.

• Project — where the task lives; its key gives the task its ID (DEV-1).
• Task type — Story, Bug, Task or Epic from the project preset. The type decides which extra fields appear at the bottom of the form.
• Priority, assignees, parent task, start and due dates — optional.
• Title and Description — the description is a full markdown editor.

The form tells you where the task will land: the task starts at the initial status of the “Software Dev” workflow.

Write the description for an agent

The description is the brief an AI step works from. What matters is the same thing that matters for a person:

• what should exist when this is done;
• where in the code it belongs, if you already know;
• how to tell it worked — the command, the endpoint, the expected output.

A task titled Add a greeting endpoint with the description Expose GET /hello that returns a greeting is enough to start. Vaguer than that, and the planning step spends its first attempt guessing.

Note

Assignees may show No members available on a fresh project — a project starts with no members. Add people to the project if you want to assign the task; it is not required for running a pipeline.

The task page

The task page carries everything that happens afterwards: description, sub-tasks, properties on the right (status, priority, resolution, type, reporter, branch), and a row of tabs — Pipeline, Changes, Files, Comments, Work — that fill up as a run progresses.

Right above the tabs is the button you need next: Run “Feature delivery”.

Next

Run it with your agent.