> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/task-sequences/creating-a-task-sequence.md).
# Creating a Task Sequence
To create a task sequence, start from scratch or use a predefined template. To start from scratch, navigate to the **Task sequences** node, click **+ Add**, and select **Add empty** from the drop-down menu.
A new version is then created with a single empty group. Click **Edit mode** to make changes. When you are finished, click **Save all changes**.
To create a task sequence from a template, click **+ Add** and select **Add from template**. Choose a template from the available list, then click **Clone**:
A task sequence and version are automatically created as a copy (clone) of the selected template. Click **Edit mode** to make changes. Ensure that the required step settings (for example, the operating system to be applied) are configured before clicking **Save all changes**.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.2pintsoftware.com/deployr/task-sequences/creating-a-task-sequence.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
