> 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-xsoar-8-on-prem/8.10/configure-cortex-xsoar/playbooks/plan-your-playbook.md). # Plan your playbook Plan a playbook for Cortex XSOAR 8.10 On-prem. When defining the work flow of your playbook, consider the following: * What actions do you need to take? * What conditions do you need along the way? Are these conditions manual or automatic? * Do you need to include looping? * Are there any time-sensitive aspects to the playbook? * When is the incident considered remediated? Example 14. Review the Phishing use case Review the following workflow for a phishing use case. Also, review the playbooks in the [Phishing content pack](https://cortex.marketplace.pan.dev/marketplace/details/Phishing/) to see how they work. * Detection * Identification * Analysis * Remediation Each of these high-level processes can contain a number of sub-processes that require step-by-step actions, all of which can be automated with either customized or new playbooks. Example 15. Review the Default Playbook The **Default Playbook** provides generic capabilities for automated incident enrichment and severity calculations that you can adjust for your needs. Watch [this video](https://www.youtube.com/watch?v=uP30BtZ_xxg) for more details. --- # 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/playbooks/plan-your-playbook.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.