> 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-cloud-posture-management/cases-and-issues/investigation-and-response/automation/playbooks/playbook-development-checklist.md).
# Playbook development checklist
The playbook development checklist follows the logical flow for developing a playbook.
We recommend that you review the following steps to successfully implement your playbook.
| Step | Details | See More |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Step 1. Plan your playbook | During the initial planning stage when designing your use case, start defining the playbook flow.
Consider the process you want to automate and the steps and the decisions during the process. These steps and decisions become the playbook tasks.
| [See topic](/cortex-cloud-posture-management/cases-and-issues/investigation-and-response/automation/playbooks/plan-your-playbook.md) |
| Step 2. Build your playbook | • Use a playbook out-of-the-box, customize an existing playbook, or create a new playbook from scratch.
• Consider using the Automation Engineer agent to create, modify, and query playbooks (preview).
• Create playbook tasks, inputs, and outputs. Maintain playbook versioning to keep track of playbook development history.
| [See topic](/cortex-cloud-posture-management/cases-and-issues/investigation-and-response/automation/playbooks/build-your-playbook.md) |
| Step 3. Customize your playbook | Fine tune your playbook for your needs, including extracting indicators, extending context, and adding issue fields to the system. | [See topic](/cortex-cloud-posture-management/cases-and-issues/investigation-and-response/automation/playbooks/build-your-playbook/customize-your-playbook.md) |
| Step 4. Test your playbook | Debug errors in your playbook. Use playbook metadata to troubleshoot playbook performance. | [See topic](/cortex-cloud-posture-management/cases-and-issues/investigation-and-response/automation/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 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-cloud-posture-management/cases-and-issues/investigation-and-response/automation/playbooks/playbook-development-checklist.md?ask=&goal=
```
`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.