> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/guides/docs-workflow-optimization.md).

# Docs workflow optimization

- [Introducing AI into your product documentation workflow](https://gitbook.com/docs/guides/docs-workflow-optimization/introducing-ai-into-your-product-documentation-workflow.md): Discover how you can use AI tools to improve your docs workflow — including its limitations and how to overcome them
- [Build your docs around your users’ needs with documentation personas](https://gitbook.com/docs/guides/docs-workflow-optimization/documentation-personas.md): With documentation personas, you can focus on the challenges your users are facing, what they need to achieve, and how your docs can help them get there
- [7 ways to make your public documentation more useful for users](https://gitbook.com/docs/guides/docs-workflow-optimization/7-ways-to-make-your-public-documentation-more-useful-for-users.md): Tips and advice to help you create great documentation, so you can improve your user ratings and reduce your support team’s load
- [10 quick tips to improve your technical writing workflow in GitBook](https://gitbook.com/docs/guides/docs-workflow-optimization/quick-tips-to-improve-your-technical-writing-workflow-in-gitbook.md): 10 practical GitBook tips for technical writers to ship better docs faster — including Markdown, keyboard shortcuts, integrations, Git Sync and more


---

# 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://gitbook.com/docs/guides/docs-workflow-optimization.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.