> For the complete documentation index, see [llms.txt](https://docs.jugalbandi.opennyai.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jugalbandi.opennyai.org/introduction/why-dive-in-how-will-this-playbook-help-you.md).

# Why dive in: How will this playbook help you?

**Empowerment:** This playbook serves as a comprehensive guide to Jugalbandi, enabling both functional and technical professionals from various backgrounds to grasp its features, components, and potential applications.

**Deepen understanding:** We also aim to engage people towards a deeper understanding of the capabilities, challenges, ethical considerations, and opportunities surrounding not just Jugalbandi but also other similar conversational AI stacks, particularly in the context of social impact initiatives.

**Innovation:** By democratising the know-how of Jugalbandi's capabilities, we aim to inspire professionals to explore innovative use cases and integrations, fostering continuous innovation on Jugalbandi.

**Collaboration:** Encouraging collaboration across different domains, the playbook facilitates knowledge sharing and collective problem-solving to maximise Jugalbandi's impact.

**Ecosystem Expansion:** Equipped with essential knowledge and tools, professionals can contribute to expanding the current Jugalbandi ecosystem, attracting more stakeholders to further enhance the platform.

**Accessibility:** it's not just the Jugalbandi stack that is accessible, the design principle cuts across all our efforts - documentation, benchmarking &  dataset creation.

<br>


---

# 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://docs.jugalbandi.opennyai.org/introduction/why-dive-in-how-will-this-playbook-help-you.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.