> 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/desktop-client/requirements-management/subrequirements.md).
# Subrequirements
Manage and organize subrequirements efficiently within the desktop client’s requirements management module. Streamline project tracking and ensure clear structure in your workflow.
In subrequirements, a full product specification sheet of a software can be specified in chapters and subchapters. These allow you to divide your chapters into standalone requirements. They can be assigned to different users and have different status, test cases and defects. So you will be able to monitor your process. In the end, you can merge everything together in one document, which can include all executed test cases, closed and known defects, and calculated parameters.
First, start by opening a single requirement and click on the Subrequirements button.Here, you can create new chapters. Click on to create a new sub requirement.
We can specify this in *Chapter 1*.
If you want to create chapter 1.1 mark Chapter 1 on the left-hand side and click on Add.
This chapter has to be moved to the right-hand side in order to create a subchapter. Mark the second chapter and click on . You will receive the following result.
If you want to edit these chapters, click on Quick edit.
---
# 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/desktop-client/requirements-management/subrequirements.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.
