Skip to content

drupal plan run

Jump to bottom
Paulo Maia Carvalho edited this page Jun 9, 2026 · 1 revision

drupal-plan-run

Execute a DrupalClaw plan step by step, updating checkboxes in the plan file as each step completes.

Usage

/drupal-plan-run <plan-id>

Typically triggered from the Plans panel in the DrupalClaw UI rather than typed manually.

What it does

  1. Loads the plan from .piclaw/plans/<plan-id>.md
  2. Sets plan status to running
  3. Executes each - [ ] step in the ## Steps section one at a time
  4. After each step (success or failure), marks the checkbox [x] via sed
  5. Writes a run log to .piclaw/plans/runs/<plan-id>-<timestamp>.log
  6. Sets final status to completed (all steps done) or failed (steps remain unchecked)
  7. Updates status: and updated: frontmatter and appends a run entry to runs:

Plan file format

Plans are Markdown files with YAML frontmatter:

---
id: abc123
title: Install and configure Redis
status: ready
created: 2026-05-01T10:00:00Z
updated: 2026-05-01T10:00:00Z
runs: []
---

## Steps

- [ ] Install the Redis module via Composer
- [ ] Enable the redis module
- [ ] Configure cache backends in settings.local.php
- [ ] Rebuild caches

## Verification

- [ ] `drush status` shows Redis as cache backend
- [ ] Cache hit rate > 80% in drupal-perf output

Step execution rules

  • Steps run one at a time — the agent executes the action, then immediately marks the checkbox
  • If a step fails, it is still marked [x] and execution continues unless later steps depend on it
  • Verification checkboxes are not executed by this skill — use drupal-plan-validate for that

Notes

  • This is an internal operation — the skill never outputs a 💡 How to replicate manually: block
  • Plans are stored under /workspace/.piclaw/plans/ which is not tracked in git
  • Run logs persist in .piclaw/plans/runs/ for audit purposes

Related skills

Clone this wiki locally