> 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.13/configure-cortex-xsoar/playbooks/playbook-development-checklist.md).

# Playbook development checklist

Follow the playbook development checklist in Cortex XSOAR 8.13 On-prem.

The playbook development checklist follows the logical flow for developing a playbook.

![playbook-development-flow-3.png](https://3790991131-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvksWgzvBZ9ZvAg4dGLrH%2Fuploads%2Fgit-blob-55693eda24d05389817befa9523ba12deea50549%2F86a6850618ca75e0fea6e52aa9d1eb9e5eaf4c2ae2f357a39270cafcb496b233.png?alt=media)

We recommend that you review the following steps to successfully implement your playbook.

| Step                            | Details                                                                                                                                                                                                                                                           | See More                                                                                              |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Step 1. Plan your playbook      | <p>During the initial planning stage when designing your use case, start defining the playbook flow.</p><p>Consider the process you want to automate and the steps and the decisions during the process. These steps and decisions become the playbook tasks.</p> | [See topic](/cortex-xsoar-8-on-prem/8.13/configure-cortex-xsoar/playbooks/plan-your-playbook.md)      |
| Step 2. Develop your playbook   | Consider whether to customize an existing playbook or create a new playbook from scratch. Create playbook tasks, inputs, and outputs. Maintain playbook versioning to keep track of playbook development history.                                                 | [See topic](/cortex-xsoar-8-on-prem/8.13/configure-cortex-xsoar/playbooks/develop-your-playbook.md)   |
| Step 3. Customize your playbook | Fine tune your playbook for your needs, including extracting indicators, extending context, and adding incident fields to the system.                                                                                                                             | [See topic](/cortex-xsoar-8-on-prem/8.13/configure-cortex-xsoar/playbooks/customize-your-playbook.md) |
| Step 4. Debug your playbook     | Debug errors in your playbook. Use playbook metadata to troubleshoot playbook performance.                                                                                                                                                                        | [See topic](/cortex-xsoar-8-on-prem/8.13/configure-cortex-xsoar/playbooks/debug-your-playbook.md)     |


---

# 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.13/configure-cortex-xsoar/playbooks/playbook-development-checklist.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.
