> For the complete documentation index, see [llms.txt](https://planetz.gitbook.io/planetz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://planetz.gitbook.io/planetz/the-product-screen-by-screen/workflows.md).

# Workflows

> Status: The product · Target version 0.1.x ｜ Verify labels against your build

## What you'll learn

What a workflow is, how Planetz picks one for you automatically, and where to browse or author your own.

***

## What a workflow is

A workflow is the **process** an agent run follows — its steps, roles, and the points where a human must approve. Workflows are defined as **YAML**, so they can be read, diffed, versioned, and shared. That's what makes a Planetz process auditable and reproducible, rather than a prompt trapped in one chat. See [The harness](/planetz/core-ideas/harness-governance.md).

## Automatic selection

You usually don't choose a workflow by hand. With **Auto** mode, Planetz reads your task description, classifies it, and **routes it to the right workflow** — showing a routing preview with the match and its reasoning. You can always switch to a specific workflow, and your choice is recorded.

## The catalog

Workflows live in a catalog (under **Settings**), grouped so you can find and manage them:

* **Core** — built-in workflows that ship with Planetz.
* **Library** — additional packs you can enable.
* **Project / User** — your own workflows, saved as YAML in the workspace and editable.

You can search, pin a workflow into the picker, hide one, or copy a core/library workflow into your project to edit it as YAML.

## Human approval gates

Workflows are where you define **where a human must approve** — before risky steps like deploy or delete. This is the harness's one honest gate: irreversible, real-world actions are staged for a deliberate confirmation (optionally a physical one via **Manta**), while reversible work runs freely. See [The harness](/planetz/core-ideas/harness-governance.md).

## Next

* [The standard workflow](/planetz/the-standard-workflow/standard-workflow.md) — the end-to-end loop these pieces form.
* [Settings & integrations](/planetz/the-product-screen-by-screen/settings.md) — where the catalog and providers are configured.


---

# 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:

```
GET https://planetz.gitbook.io/planetz/the-product-screen-by-screen/workflows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.