> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/~/revisions/hfepfFy5E9C1WpLCChmV/project-manual/team-lead.md).

# Team lead

as the team lead, you lead and organize the project team while at the same time being an active contributing part of the team. In this section you can learn more about this very important role.

{% hint style="warning" %}
under construction

you can find some first information in the slide deck below. Please contact Frie if you are interested in learning more!
{% endhint %}

### Mural Templates

We have developed some Mural templates that you can use for the kickoff. You can download a PDF overview here. If you want to use some of the templates for your project kickoff, please reach out to Frie and they'll create a Mural dashboard for you.


---

# 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.correlaid.org/~/revisions/hfepfFy5E9C1WpLCChmV/project-manual/team-lead.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.