> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/getting-started/feature-requests.md). # Feature Requests "The art of great business is being a great middle man" - Eddie Temple | Layer Cake Our goal with Roadmap is to provide a single native ecosystem, and hearing feedback from our brands is highly valued and appreciated. We welcome insights and requests to improve the platform, but, as humans, focusing on quality, we review each request on its merits and ensure that before time or resource investment, it is likely to benefit the wider collective of brands and partners on Roadmap. If you need further support which is specific to your website, then these types of requests are more suited to an agency engagement of work, not a Roadmap feature request. We are nice humans, who like working with nice humans, so any requests that do not full into Roadmap services should be refered to your studio or agency partner. --- # 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.roadmap.so/getting-started/feature-requests.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.