> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/aqua-intelligence/create-requirements-with-ease-with-aqua-intelligence/create-user-stories-bdds-or-prds-based-on-a-file.md).

# Create user stories, BDDs, or PRDs based on a file

Need user stories, BDDs, or PRDs? Our aqua Intelligence transforms any file into instant documentation, putting your agile workflow on the fast track. No more manual requirements mapping.

With aqua Intelligence users can quickly generate User Stories, Behavior-Driven Development (BDD) requirements, or Product Requirements Documents (PRD) based on files they upload. Supported file formats include images (png, jpg, webp, tiff), xlsx, and PDFs. This feature is designed to speed up requirement documentation by leveraging pre-existing materials and transforming them into actionable requirements.

When creating the requirement with aqua Intelligence, select **the 'File' as input option and upload your file.** Click 'Browse' or drag and drop your file into the designated area.

Provide additional context in case you find it important for aqua Intelligence to consider.

Choose between creating a **user story**, **BDD**, or **PRD**. and click 'Create' button.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FZ6a843L2Cf5Olkr1Rngz%2Fimage.png?alt=media&amp;token=96e0556a-3af5-4042-9a3d-8a85f0b55b4e" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FQp0k4PjBWZRn1CnaATw7%2Fimage.png?alt=media&amp;token=2d7b6cb7-1464-4bd8-aad1-1a71004ddcde" alt=""><figcaption></figcaption></figure>

After the document is generated, you can review the content, make any necessary edits, and add it.

If you don't like the result, click 'Regenerate' icon.

You can create requirements based on the files from the requirements page too. Just click the button 'Write' and use it as from the navigation page.

<figure><img src="https://3920520305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyZbW8vbNs5hz8x57emJJ%2Fuploads%2FqAaIdFLmgxU7ajLS37sf%2Fimage.png?alt=media&amp;token=e4aa5472-bb90-4ae8-9e50-bb953eee5a8b" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please note that while this feature is in beta, it has a few limitations:

* It can generate only one document at a time.
  {% endhint %}

You can create one or multiple User Stories or features written in the Gherkin format at a time!

Check out the next page for mutliple items output [Create multiple user stories or BDDs with aqua Intelligence](/documentation/aqua-intelligence/create-requirements-with-ease-with-aqua-intelligence/create-multiple-user-stories-or-bdds-with-aqua-intelligence.md)


---

# 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.aqua-cloud.io/documentation/aqua-intelligence/create-requirements-with-ease-with-aqua-intelligence/create-user-stories-bdds-or-prds-based-on-a-file.md?ask=<question>&goal=<user_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.
