> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/documentation/workflows/playbooks.md).

# Playbooks

The 12 built-in Playbooks, their modes and requirements, and how to copy, edit and save your own.

A Playbook is a ready-made job: instructions, inputs, the tools and integrations it needs, and the modes it supports. Open **WP AI Manager > Playbooks > Library**. Playbooks are grouped by category: Content, SEO, Design, Store and Maintenance.

## Modes

| Mode         | What happens                                                                                                                               |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Ask**      | Opens Chat with the playbook's instructions.                                                                                               |
| **Guided**   | Shows a short form, validates required fields and choices, then starts Chat. Preparing the form does not call the model or write anything. |
| **Automate** | Opens the Task review screen. Choose **Run now**, or set a schedule. Opening the link does not run it.                                     |

If a requirement is missing, the card shows **Needs X** linking to Integrations, and Automate is greyed out with the reason.

## Built-in Playbooks

| Playbook                         | Category    | Modes            | Requires                                      | Can schedule |
| -------------------------------- | ----------- | ---------------- | --------------------------------------------- | ------------ |
| Write a blog post                | Content     | Guided, Automate | Nothing; SEO plugin and stock images optional | Yes          |
| Create a contact form            | Content     | Guided           | A supported form plugin                       | No           |
| Write SEO meta for this page     | SEO         | Ask, Guided      | Rank Math, Yoast SEO or Slim SEO              | No           |
| Fix missing SEO meta (site-wide) | SEO         | Automate         | Rank Math, Yoast SEO or Slim SEO              | Yes          |
| Build a landing page             | Design      | Guided           | Elementor                                     | No           |
| Apply my brand colors and fonts  | Design      | Guided           | Elementor (active kit)                        | No           |
| Put a category on sale           | Store       | Guided           | WooCommerce 10.9+                             | No           |
| Add missing image alt text       | Maintenance | Automate         | Nothing (a vision model gives better text)    | Yes          |
| Update text everywhere           | Maintenance | Guided           | Nothing                                       | No           |
| Fix broken links and 404s        | Maintenance | Guided, Automate | Redirects module                              | Yes          |
| Site health check                | Maintenance | Ask, Automate    | Nothing (read-only)                           | Yes          |
| Back up my site                  | Maintenance | Automate         | Nothing; UpdraftPlus optional for full site   | Yes          |

For a block-editor landing page, ask in Chat ("Build a landing page in the block editor"); a bundled Gutenberg landing-page skill handles it.

## Find a Playbook fast

* Press **Cmd+K** / **Ctrl+K** anywhere in wp-admin and type a name or keyword. See [In-editor assistant and command palette](/documentation/workflows/in-editor-assistant-and-command-palette.md).
* In Chat, use **Find a playbook** or type **/**.

## Make your own

* **Duplicate and edit** on a built-in creates a private copy. Edit its title, instructions and inputs. The original and its schedules are not changed.
* **Edit my copy** and **Move to Trash** appear on your copies.
* **Save as playbook** in Chat saves a conversation as a Playbook. A recurring one also creates an automation.

## Under the hood: Tasks, Skills and Prompts

**Playbooks** has three more sections for direct editing:

* **Tasks and runs**: Task recipes, Run history, schedules and automations. See [Tasks and schedules](/documentation/workflows/tasks-and-schedules.md).
* **Skills**: written instructions the assistant loads for a job. Built-ins cover accessibility quick fixes, applying a Brand Kit, blog brand voice, a contact page with a form, Elementor and Gutenberg landing pages, on-page SEO, speed quick wins and WooCommerce product listings.
* **Prompts**: your saved prompts.

## Example: Put a category on sale

1. Choose **Put a category on sale** > **Guided**.
2. Pick the category and percentage, and optional start and end dates.
3. The assistant runs a **dry run** and shows affected products and new prices.
4. Approve on the card to apply. The tool is bound to the inputs you validated, so the model cannot change the category, percentage or dates.
5. Check the products in WooCommerce. Undo is available from the result card or History.

See [Content, SEO and store workflows](/documentation/workflows/content-seo-and-store.md) and [Build pages and forms](/documentation/workflows/build-pages-and-forms.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://docs.3techagency.com/documentation/workflows/playbooks.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.
