> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/worlds-design/designing/exercise-setup.md).
# Exercise setup
To add details to your exercise, select the space which your exercise is uploaded to. You will be able to configure this scenario.
Here you have the option to add key details about the exercise.
{% tabs %}
{% tab title="Description" %}
An overview of your exercise - what happens in the scenario?
{% endtab %}
{% tab title="Exercise Type" %}
Use this field to build your own categories of exercises. For example, Cyber, Reputation, etc
{% endtab %}
{% tab title="Difficulty Level" %}
This might refer to the training audience proficiency or to the facilitator proficiency - it’s up to you!
{% endtab %}
{% tab title="Exercise Objectives" %}
Enter the key training objectives
{% endtab %}
{% endtabs %}
And go into further detail by also adding:
{% tabs %}
{% tab title="Audience" %}
Who is the training audience, what roles/departments are there, what is the required skill level, prerequisites?
{% endtab %}
{% tab title="Specifications" %}
Document where participants are located, what role they have, what equipment is needed, prerequisites, etc.
{% endtab %}
{% tab title="Key Elements" %}
Explain key content, key positions, key players and key injects.
{% endtab %}
{% tab title="Supporting Documents" %}
This is visible to facilitators and shows a time-stamped entry every time you publish the exercise. You can manually edit the entries.
{% endtab %}
{% endtabs %}
---
# 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://helpdocs.conducttr.com/worlds-design/designing/exercise-setup.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.
