> For the complete documentation index, see [llms.txt](https://mind-expression-docs.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mind-expression-docs.gitbook.io/home/how-to-guides/steps.md).

# Steps

Steps are useful to manage the conversation flow when it gets more complex, for example by having multiple Components. It helps you organize the flow better and easily look at the whole picture. Every step is required to include one top-level Component, and it can have child Components if necessary; to add a new sibling Component, you need to add another Step.

{% embed url="<https://mind-expression.s3.ap-northeast-2.amazonaws.com/dev/static/video/en/how_to_guide_steps.mp4>" %}

### Add Steps

You can add a Step only if there is at least one Component in the current Step.

1. Click on the add button.
2. Enter the name.

### Rearrange Steps

You can change the sequential order by moving the Steps. Just drag a Step to where you want to place it.

### Edit Steps

You can modify the name of a Step.

1. Open the more actions menu.
2. Click **Edit**
3. Enter the new name
4. Click the save button

### Delete Steps

1. Open the more actions menu.
2. Click **Delete**.
3. In the popup, confirm and click **Delete**.


---

# 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://mind-expression-docs.gitbook.io/home/how-to-guides/steps.md?ask=<question>&goal=<endgoal>
```

`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.