> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/automations/playbooks/plan-your-playbook.md).

# Plan your playbook

When defining your playbook workflow, consider these questions:

* Which processes need automation?
* Which decisions need manual intervention?
* Does automation require dynamic decisions or complex data interpretation?
* Which parts of the workflow are time-sensitive?
* When is the case considered remediated?

### Example: Review the phishing use case

Review the phishing workflow below. You can also review playbooks in the [Phishing content pack](https://cortex.marketplace.pan.dev/marketplace/details/Phishing/).

* Detection
* Identification
* Analysis
* Remediation

Each high-level process can contain several sub-processes. You can automate these actions with customized or new playbooks.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/automations/playbooks/plan-your-playbook.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.
