# Creating Feature Requests

elementary uses GitHub Issues both for reporting problems and for tracking feature requests. In addition to what's been mentioned in [Reporting Issues](/contributor-guide/feedback/reporting-issues.md), keep in mind the following tips when creating new feature requests:

### Describe The Problem

It's often tempting when creating a feature request to only describe the proposed solution, but don't forget to fully describe the problem that your proposal is meant to solve. Describing the problem is an essential step to ensure that a proposed design meets its goals.

{% hint style="info" %}
If you're having trouble describing the problem in a concise way or it involves a larger design change rather than a single new feature, consider [starting a discussion](/contributor-guide/feedback/starting-discussions.md) instead
{% endhint %}

### Include Mockups or Prior Art

If you can, include a mockup or a sketch of what your proposed new feature would look like. Or, if there's another project that implements this feature, include screenshots or links to that project.

### Consider Alternatives

If there could be alternative solutions to your intial problem, describe them and their merits. A developer may decide that a certain specific feature request is out of scope for a project or conflicts with its other design goals, but if you include alternative solutions one of those may work better and be accepted as a solution.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.elementary.io/contributor-guide/feedback/creating-feature-requests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.