> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/fabricate/databases-and-data/simulations/simulation-start.md).
# Starting a simulation
## Composing the simulation scenario prompt
Every simulation starts with a prompt that describes the simulation scenario to Fabricate. The scenario has a central character, or persona, who is the focus of the scenario.
Here is an example of a very basic prompt:
`Change to simulation approach, and generate an exchange of email messages and Slack messages over the course of a day between a development manager and a product manager about an upcoming new product feature. The messages discuss the design and the proposed staffing. Include a design documents in Google workspace.`
A scenario can also be a more detailed Markdown file that you attach, with more specific details about the actors and events.
## Creating the simulation workflow
To create a simulation workflow, you use the Simulation approach.
To change to the Simulation approach manually, click the mode indicator, then select **Simulation**.
Data Agent mode and approach menu with the Simulation approach option
The Data Agent can also automatically change to the Simulation approach based on your prompt.
To start a workflow, prompt the Data Agent and provide the scenario. For a shorter scenario, you can type or paste the scenario directly in the Data Agent prompt. You can also attach a Markdown file that contains the scenario details.
The Data Agent analyzes the scenario and asks any clarifying questions to guide it in the workflow creation.
---
# 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://docs.tonic.ai/fabricate/databases-and-data/simulations/simulation-start.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.
