> For the complete documentation index, see [llms.txt](https://docs.oscafrica.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oscafrica.org/contributing/issue-labels.md). # Issue Labels ### Engineering *Coming soon* ### Design | Label name | Description | | -------------------- | ----------------------------------------------- | | design-approved | Design ready for development | | design-in-progress | On going design task | | design-ready | Design is ready for review | | design - Stalled | Something isn't working | | design-issue | Issues related to design | | design-documentation | Improvements or additions to the documentation | | duplicate | This issue or pull request already exists | | enhancement | New feature or request | | good first issue | Good for newcomers | | Graphics | Graphics related issues | | help wanted | Extra attention is needed | | Ideation | Design ideas we're thinking about but not doing | | invalid | This doesn't seem right | | question | Further information is requested | | social media & PR | Design issues related to social media & PR | | UI/UX | Issues related to web design | | Website | Issues related to website | | wontfix | This will not be worked on | ### Documentation *Coming soon* --- # 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.oscafrica.org/contributing/issue-labels.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.