> For the complete documentation index, see [llms.txt](https://help.cloudjournals.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cloudjournals.com.au/the-core/plan/tasks.md).
# Tasks
Tasks are the steps you need to take to get closer to your Goal. The Task list for a particular Goal can be seen, as shown below, when you view a Goal in detail by clicking on it.
Tasks are ordered according to their [priority](/the-core/plan.md#priority) (determined by the due dates you set for them).
## Create a Task
To create a new Task, click the ***Add Task*** button at the bottom of the *tasks card* while viewing a Goal in detail. A modal will appear with fields to fill out; all fields are required. Once you've entered your Task details, click ***Save***.
## Manage a Task
Whether you are viewing the Task from within the Goal itself or via the [Progress](/the-core/plan.md) tab located in the Plan section, you can use the context menu to the right of the Task to edit, delete, mark it as (in)complete or link files.
### Edit
From the Task context menu , click ***Edit.*** . You will see fields filled out with your information. Make your changes, then click ***Save***.
### Mark Complete / Incomplete
From the Task context menu, click the Context Menu ***Mark Complete*** or ***Mark Incomplete*** to change the Task's status. The Task will be moved to the relevant [Priority](/the-core/plan.md#priority) list within its associated Goal.
### Delete
From the Task context menu, click ***Delete*** and confirm the dialogue. **Please note this cannot be undone**.
## View a Task
To view a Task in detail, click the *drop down* button to the right of the Task. This can be done anywhere a Task is listed, including in [Progress](/the-core/plan.md) and the \[Goal view] \[View Goal].
\[View Goal]: /plan/goals.md#view-goal "View Goal"
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.cloudjournals.com.au/the-core/plan/tasks.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.