> For the complete documentation index, see [llms.txt](https://docs.openstamanager.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openstamanager.com/2.5.5/openstamanager/modules/strumenti/checklists.md).
# Checklists
Come gestire le Checklists in OpenSTAManager
{% hint style="info" %}
Il modulo **Checklists** permette di aggiungere e modificare le checklists da utilizzare nel plugin Checklist.
{% endhint %}
## ➕ Creazione
Per creare una nuova checklist si dovrà cliccare sul tasto (+).
Andranno qui inserite le informazioni relative alla nuova checklist:
* Nome
* Modulo del template
* Plugin del template
## 🖌️ Modifica
Cliccando sul record da modificare si aprirà la schermata di dettaglio, da cui sarà possibile modificare:
* Nome
* Modulo/Plugin del template
* Contenuto
* Genitore
* Decidere se utilizzare l'elemento padre come titolo
### Utilizzo delle checklist nei moduli
Per richiamare il template di una checklist in un determinato modulo sarà sufficiente accedere al plugin Checklist e richiamarla tramite l'apposito pulsante:
{% content-ref url="/pages/-MWPgr98l6w1wBfuG2v0" %}
[Checklist](/2.5.5/openstamanager/modules/attivita/plugin/checklist.md)
{% endcontent-ref %}
---
# 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.openstamanager.com/2.5.5/openstamanager/modules/strumenti/checklists.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.
