> For the complete documentation index, see [llms.txt](https://cqube.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cqube.sunbird.org/standard-operating-procedure/suggesting-enhancements.md).

# Suggesting Enhancements

Describes the process of suggesting enhancements for cQube to the cQube Product Team

Any new feature enhancement can be suggested by the cQube adopters based on the needs realised. 

### Communication Tool

All the requests for support should be posted as Ideas on the cQube Discussion Forum on GitHub - [Link](https://github.com/Sunbird-cQube/community/discussions/categories/ideas).

### Suggesting Enhancements on GitHub

A new discussion should be created in the GitHub Discussion Forum of cQube **only** if any similar discussion doesn't already exist or has been answered by the cQube Product Team. The unanswered / open discussions for cQube can be seen [here](https://github.com/Sunbird-cQube/community/discussions/categories/ideas?discussions_q=category%3AIdeas+is%3Aopen) and the closed discussions can be seen [here](https://github.com/Sunbird-cQube/community/discussions/categories/ideas?discussions_q=category%3AIdeas+is%3Aclosed).

**Process to initiate an idea:**

1. Go to the Ideas tab of cQube Discussion Forum on Github - <https://github.com/Sunbird-cQube/community/discussions/categories/ideas>

<figure><img src="https://720888978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Miy6UN-HyTKGo2Sjcky%2Fuploads%2FKTQZ6IcY3Ucmibbhucri%2Fimage.png?alt=media&amp;token=8d69d3f7-ec17-44b7-9318-16e7dbcbadc1" alt=""><figcaption></figcaption></figure>

2. Start a new discussion.
3. Detail out the enhancement that you are suggesting with a title and description. You can add any images for context on the suggestion.

<figure><img src="https://720888978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Miy6UN-HyTKGo2Sjcky%2Fuploads%2FVakjSGzfnlD3Kkx3xTsG%2Fimage.png?alt=media&amp;token=f5034658-d954-4e0d-aad3-c7e774352df5" alt=""><figcaption></figcaption></figure>

4. Attach relevant label(s) to the enhancement being suggested.

<figure><img src="https://720888978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Miy6UN-HyTKGo2Sjcky%2Fuploads%2F7FDcATQrMDJcd02qm1Ki%2Fimage.png?alt=media&amp;token=6b4cc438-db54-4bfc-8b4e-b1d30469d899" alt=""><figcaption></figcaption></figure>

5. Click on 'Start Discussion'

### Response from the cQube Product Team

The cQube Product Team will get back within 7 working days post the enhancement has been suggested. If relevant, it will be included in the cQube roadmap with a timeline. The adopter who has suggested the enhancement will be able to track it on a JIRA ticket.


---

# 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://cqube.sunbird.org/standard-operating-procedure/suggesting-enhancements.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.