> 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/compose-document/why.md).

# Why?

### **Why use Compose Document?**

Compose Document allows you to combine your legal expertise with AI to help you draft complete, well-structured documents quickly and efficiently from scratch. It supports creating outlines, generating clauses, and adapting content, all while allowing you full control over the final result.

✅ **When you *****should***** use it:**

* **To speed up drafting**\
  Combine AI power with your own clause library to draft documents faster.
* **To create structured content**\
  Generate detailed outlines and clauses with clear instructions.
* **To edit and adapt easily**\
  Quickly rephrase, add, or modify clauses to fit your needs and style.
*  **To draft diverse documents**\
  Use it for contracts, memos, letters, or isolated clauses.

***

❌ **When you *****shouldn’t***** use it:**

* **If you need full manual control**\
  If you want to write everything without AI assistance.
* **If you require specific legal advice**\
  When the document needs very precise, expert legal input tailored to its unique context, AI may not be sufficient on it's own.
* **If you avoid templates or AI**\
  If you prefer drafting without templates or AI-generated suggestions.


---

# 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/compose-document/why.md?ask=<question>&goal=<user_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.