-
Notifications
You must be signed in to change notification settings - Fork 0
drupal plan validate
Paulo Maia Carvalho edited this page Jun 9, 2026
·
1 revision
Validate a DrupalClaw plan by running the checks in its ## Verification section and updating the plan status accordingly.
/drupal-plan-validate <plan-id>
Typically triggered from the Plans panel in the DrupalClaw UI rather than typed manually.
- Loads the plan from
.piclaw/plans/<plan-id>.md - Reads the
## Verificationsection - Runs each
- [ ] checkone at a time - If a check passes → marks it
[x]; if it fails → leaves it as- [ ] - Sets final status to
completed(all checks pass) orfailed(some checks fail) - Updates
status:andupdated:frontmatter
Run after drupal-plan-run to confirm the plan's outcome:
- Module is installed and enabled
- Configuration is correct
- Site is reachable and functional
- Cache backend is active
Add a ## Verification section to any plan with testable assertions:
## Verification
- [ ] `drush pm:list --status=enabled | grep redis` shows the module enabled
- [ ] `drush status` shows Redis as the cache backend
- [ ] Site loads without errors at the configured URLChecks can be commands, file existence tests, HTTP requests, or any assertion the agent can evaluate.
- Validation is separate from execution intentionally — you can re-run validation without re-running all steps
- This skill never outputs a
💡 How to replicate manually:block - A plan without a
## Verificationsection will complete immediately with no checks run
- drupal-plan-run — execute the plan steps before validating
- drupal-debug — diagnose issues if validation fails