> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/playbooks/what.md).
# What?
### **What are Playbooks?**
The Playbooks feature allows you to analyse documents using Large Language Models (LLMs) combined with explicitly specified review rules ("Playbooks"). Instead of relying solely on general AI knowledge, the feature applies your organisation’s internal rules and criteria to review documents accurately and consistently.
By breaking documents into clauses and paragraphs, the system cross-checks each part against your custom rules and provides detailed feedback with references to relevant sections. This approach ensures practical, deal-specific and internal guidelines are respected in the review process.
The feature acts as a digital playbook that helps legal teams enforce internal policies, improve knowledge sharing, and accelerate onboarding, while leveraging AI to assist in automating and supporting contract review tasks.
---
# 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://help.clausebuddy.com/playbooks/what.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.
