> 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-xsiam/configure-cortex-xsiam/automations/autonomous-playbooks/work-plan-for-autonomous-playbooks.md).

# Work Plan for autonomous playbooks

To keep incident investigations highly focused, the system abstracts underlying conditions and background scripts. When you view an autonomous playbook in an issue's resolution tab, it opens a unique, curated Work Plan. This view presents only the executed key tasks and their defined outputs, ordered sequentially, ensuring you immediately see conclusions without the distraction of background tasks.

For tasks requiring manual intervention or approval, the Work Plan presents the step as pending user input in the resolution center in case view, providing a direct option for you to complete the task without switching pages. These manual steps also aggregate in the case's pending tab so you can manage all required user inputs centrally. When an autonomous playbook executes at the issue level and its results are incorporated into a case, the AI-generated case description and investigation plan summarize the exposed key actions and outputs. This ensures your AI-generated summaries remain concise and highly relevant.

If an error occurs on a visible task, the Work Plan shows a specific textual description, such as **Failed retrieving user password**. If an error happens in a background task, the system shows a general error message at the playbook level. If a playbook fails, you have the option to rerun it directly from the Work Plan. You can also provide feedback to Palo Alto Networks regarding the playbook's performance and select a proposed issue verdict.


---

# 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-xsiam/configure-cortex-xsiam/automations/autonomous-playbooks/work-plan-for-autonomous-playbooks.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.
