> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/guild-portal/guild-directory/leadership-guild.md).

# Leadership Guild

## Mission and Purpose

To act as lead roles for tech fleet's products and services.

## Roles

Head of UX

Head of Product

Head of Strategy

More leadership positions are coming, like head of technology and head of inclusion and more.

## Overview

The leadership guild of Tech Fleet is comprised of a small group of individuals who carry out thought leadership and operational leadership in the community. They work in tandem with other guilds to carry out the mission of Tech Fleet.&#x20;

## Read More in the Guild Handbook

{% content-ref url="/pages/bbZKiItinbFJJOLeitOF" %}
[Guild Handbook](/guild-portal/guild-handbook.md)
{% endcontent-ref %}

## Leadership Guild Backlog

The team manages a backlog of tasks they work weekly.

{% embed url="<https://tech-fleet-community-dao.notion.site/TF-Leadership-Guild-357acb5137ba40e9bfb154f7c641473a>" %}

## How to join the Leadership Guild

New details will be released in the future pertaining to how one can contribute to the Infrastructure Guild of Tech Fleet.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.techfleet.org/guild-portal/guild-directory/leadership-guild.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
