> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/masterstudy-theme-documentation/masterstudy-lms-pro-addons/masterstudy-theme-manual-prerequisites.md).
# Prerequisites
Prerequisites are the requirements students must complete before they can enroll in the next course of a higher level.
{% embed url="" %}
You can enable the **Prerequisites** addon in the **MasterStudy LMS Settings > Addons** section of the WordPress dashboard menu.
After that, you need to edit a course and set up the prerequisites settings of a course in the Course Prerequisites section of the [**Course Builder**](/masterstudy-theme-documentation/lms-courses-features/masterstudy-theme-manual-course-builder.md#prerequisites). Edit any course with [**Course Builder**](/masterstudy-theme-documentation/lms-courses-features/masterstudy-theme-manual-course-builder.md), and follow **Settings > Prerequisites.**
* **Prerequisite Passing Percent (%)** - specify the passing rate of prerequisite courses
* **Courses** - indicate the courses that should be completed before purchasing this course
{% hint style="success" %}
If students want to enroll in the course, they will see that it has a prerequisite, so they need to accomplish it first.
{% endhint %}
---
# 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.stylemixthemes.com/masterstudy-theme-documentation/masterstudy-lms-pro-addons/masterstudy-theme-manual-prerequisites.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.
