> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/user-documentation/dashboard/creating-a-task.md).
# Creating a Task
This lesson will show you how to create a task in AgileCase.
{% stepper %}
{% step %}
### Fill in Task Details
Once you have chosen to create a task, fill in the task details. First, create a brief description. Use the note option to flesh out the task in more detail.
Select which case the task is associated with and the date it is due before deciding which user is responsible for its completion. Once this is done, click "Save Changes" to create the new task.
{% endstep %}
{% step %}
### View Task
You can now view your task on the case page under the "Tasks" tab. Overdue tasks will be displayed with a red button, whilst tasks still on schedule will show a green button.
{% endstep %}
{% endstepper %}
---
# 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://docs.agilecase.com/user-documentation/dashboard/creating-a-task.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.