> For the complete documentation index, see [llms.txt](https://guide.kitemaker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.kitemaker.co/initiatives-roadmaps/initiatives.md).
# Initiatives
You can find the list of initiatives for a spaces under initiatives in the space:
From this screen you can both create new initiatives, reorder the initiatives, and, if your organization has roadmaps enabled, you can create a roadmap specifically to your space.
{% hint style="info" %}
Initiatives have a lot of parallels to epics from issue tracking tools. Historically, epics were high-level user stories meant to be broken down into more specific user stories. Since work items themselves are usually broader than user stories, many customers will use work items at the level they have used epics earlier and initiatives for larger bodies of work.
{% endhint %}
Each initiative has two main parts. First is the description. This can be used to explain the background, collect tasks related to forming the initiative, and add any other information that is relevant to the initiative.
The other section contains the work items connected to the initiative. You can add initiatives from the work item by selecting initiatives in the "…" menu, pressing the **`!`** hotkey, or you can manage the work items directly from the initiatives screen.
Note that you can share initiatives across spaces, and in that case, you will have an additional tab for each space to manage the work items.
## Metadata
Initiatives has many of the metadata options as work items, including impact, effort, labels, members, insights etc. You should note that some of the metadata is managed at the organization level. This includes impact, effort, and labels. To manage this, head to the "Roadmap and initiatives" section in your organization settings.
---
# 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.kitemaker.co/initiatives-roadmaps/initiatives.md?ask=&goal=
```
`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.