> 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/split-or-convert-requirements-with-aqua-intelligence.md).
# Split or convert requirements with aqua Intelligence
Learn how to split or convert project requirements efficiently using aqua Intelligence. Streamline workflows with step-by-step guidance tailored for agile teams.
Open any requirement you want to modify.
Then click on aqua Intelligence **‘Write’ option** on the ribbon. Then choose the option '**Current requirement'.**
Define requirement type:
* **User story**
**or**
* **BDD (Behavior-Driven Development)**
You can add a description to refine the generated output.
If no description is provided, aqua Intelligence uses only the requirement text.
Then select action you want aqua Intelligence to perform.
**User story**
* **Split into separate user stories**: Creates new independent user stories. The current requirement remains intact.
* **Convert to an epic with linked sub-requirements**: The requirement is converted into an epic, with user stories linked to it.
* **Convert to an epic and extend user stories**: Similar to the previous option, but with additional details added to sub-requirements.
**BDD**
* **Break down the feature into separate individual scenarios**. Converts current requirement into the document with separate scenarios.
You can preview generated user stories, keep only those that needed and/or adjust them with additional promts.
---
# 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/split-or-convert-requirements-with-aqua-intelligence.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.
