> 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/playbook-development-checklist.md).

# Playbook development checklist

Plan, build, customize, and test playbooks in Cortex AgentiX with this development checklist.

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

![playbook-development-flow-4.png](https://404732257-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FocwvgxtzkvBHMLbPsZuG%2Fuploads%2Fgit-blob-1aa5b99371ff8ce9441a32e3ac096a21688cc1f7%2Ffbaa7f7ce50858b2c608e5f14fd180ad0a6196d92d2d31774aa5d8bb52e9bbda.png?alt=media)

Review these steps to implement your playbook successfully.

| Step                            | Details                                                                                                                     | See More                                                                                                                   |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Step 1. Plan your playbook      | During planning, define the playbook flow. Consider the process, its steps, and its decisions. These become playbook tasks. | [See topic](/cortex-agentix/configure-cortex-agentix/automations/playbooks/plan-your-playbook.md)                          |
| Step 2. Build your playbook     | Use an out-of-the-box playbook, customize one, or create one. Create tasks, inputs, and outputs. Maintain version history.  | [See topic](/cortex-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook.md)                         |
| Step 3. Customize your playbook | Fine-tune the playbook. Extract indicators, extend context, and add issue fields.                                           | [See topic](/cortex-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/customize-your-playbook.md) |
| Step 4. Test your playbook      | Debug errors and use playbook metadata to troubleshoot performance.                                                         | [See topic](/cortex-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/test-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-agentix/configure-cortex-agentix/automations/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.