# Engine Guidance

You could technically let the engine take control and determine the output by repeatedly clicking on the completion button, but this will mostly result in a "derailing" effect.

For example, let's say you want to write a story about the lost city of Atlantis. The first thing that probably occurs in your mind is to start your story with a description or history of the city. Well, you quickly realize that by doing this you are essentially telling the engine what to write about. This may not be a big problem if the story is about anything but Atlantis, however, your narrative needs a hook that will make the reader want to continue reading.

{% hint style="info" %}
This is why it is so important to supervise the AI's output throughout the entire writing process and to give it some guidance on where the story should be going.
{% endhint %}

We are testing the AI as we speak and there is a lot to learn. Although the engine is still in its early stages, we are excited to see where it can take us.


---

# Agent Instructions: 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:

```
GET https://docs.writier.io/engines/engine-guidance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.