> For the complete documentation index, see [llms.txt](https://docs.lamsfoundation.org/tbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lamsfoundation.org/tbl/tbl-for-teachers/getting-started/create-tbl-lessons-with-lams-generative-ai.md).

# Create TBL lessons with LAMS Generative AI

LAMS provides an easy to use chat-bot interface to create TBL lesson plans which leverage on Generative AI to ensure that your lessons are perfectly aligned with your learning outcomes

### Create Team-Based Learning Plans Effortlessly

**LAMS Generative AI** is perfect for lecturers who want to enhance their teaching with TBL but don’t have the time for extensive planning. Whether you’re new to TBL or a seasoned expert, LAMS can support you at every step.

This is how it works:

{% embed url="<https://vids.lams.sg/demo/cm0xwc81i0094148qaqe5k317>" %}
Create TBL lesson plans effortlessly
{% endembed %}

**Prefer to design your lesson manually?** If you choose not to use Generative AI, you can still take advantage of our intuitive [TBL Wizard](/tbl/tbl-for-teachers/getting-started/tbl-design-wizard-1.md), which guides you step-by-step to create customised TBL lesson plans quickly and efficiently.


---

# 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.lamsfoundation.org/tbl/tbl-for-teachers/getting-started/create-tbl-lessons-with-lams-generative-ai.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.
