> For the complete documentation index, see [llms.txt](https://readme.directual.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.directual.com/plugins/developing-plugins/developing-scenario-plugins.md).

# Developing Scenario Plugins

At present, the steps within a plugin are [HTTP request steps](/scenarios/editing-scenarios/integration-steps/http-request-step.md). You have the flexibility to add as many scenario steps to a plugin as needed. Each step comprises the following settings:

1. **Step Appearance**: Includes the step's name and icons, which can be customized using templates.
2. **Step Parameters**: This section allows you to specify the data to be entered into the step.
3. **API Call**: Within this section, you can define the parameters for the API call. This may include both Shared parameters and Step-specific parameters.


---

# 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://readme.directual.com/plugins/developing-plugins/developing-scenario-plugins.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.