Repository navigation
Flows and Plans
Paulo Maia Carvalho edited this page Oct 2, 2026
·
1 revision
Flows are multi-step automations the agent runs in order. A step can be:
- a skill step: runs any skill (for example
drupal-cr) - a message step: sends an instruction to the agent
- an MCP step: calls a tool on a connected MCP server
A flow can be started manually or on a schedule (interval or cron expression). Parameters written as {{param}} are filled in when the flow runs. The Flows tab keeps the run history, and from a run you can analyse the output in chat or create a Plan from it.
A plan is a Markdown file in .piclaw/plans/<id>.md with YAML frontmatter: a reviewable strategy with executable steps and verification checks.
- In chat, with the Plan toggle on: the agent proposes a plan and a Save plan button appears
- Manually, with
+in the Plans tab - From a flow run, with Create plan
draft → (Execute) → running → completed / failed → (Validate) → completed / failed
| Status | Meaning |
|---|---|
draft |
Created, not executed yet |
running |
Execution or validation in progress |
completed |
All steps and checks passed |
failed |
One or more steps or checks failed |
Execute runs the steps in order and ticks the checkboxes as it goes (drupal-plan-run). Validate runs the ## Verification checks and updates them (drupal-plan-validate).
- Marketplace — skills from catalogs can be used as steps