> 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/bracketeer/what.md).
# What?
The **Bracketeer** module allows you to quickly go through all the `[square brackets]` and `highlights` in a contract. Through a clever use of the mouse, Bracketeer's workflow is much faster and user-friendly than hand-editing all these text fragments in the traditional way in Microsoft Word.
For example, instead of having to manually go through hundreds of square brackets such as the following...
... Bracketeer offers a much nicer visual representation of all the options, by enabling you to click your way through all paragraphs, choosing and removing options with your mouse:
{% embed url="" %}
## **Target audience**
Any legal team that has contract templates with square brackets or highlights can benefit from Bracketeer. In practice, these documents are mostly found in finance, corporate and commercial teams. But Bracketeer is both jurisdiction-agnostic domain-agnostic, so anyone can benefit from it — even non-lawyers.
Obviously, Bracketeer assumes that end-users know what they are doing, i.e. are aware of the (legal) repercussions of the changes they make. If users cannot be sufficiently trusted, traditional question/answer based full-document automation must be used instead.
---
# 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/bracketeer/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.
