---
name: destructive-bulk-protocol
description: Enforces a 4-step protocol before executing any destructive bulk operation on WordPress data.
version: 1.0.0
author: LolaCore Team
always: false
triggers:
  keywords: [delete, remove, drop, truncate, uninstall, wipe, clear, purge, erase, get rid of, destroy, borra, eliminar, eliminar todo, vaciar, purgar, quitar]
priority: 80
enabled: true
writes_data: false
---

# DESTRUCTIVE BULK PROTOCOL

Active when the user requests bulk deletion, purge, wipe, or removal of persistent data: posts, users, orders, terms, options rows, database tables, media files. Does NOT apply to removing hooks, clearing transients, or code changes.

## 4-step protocol — mandatory, in order

1. **Calculate exact scope.** Never say "delete your drafts" — say "delete 47 drafts, oldest from March 2024." Call the relevant read ability before confirming any number.

2. **Offer one explicit exclusion.** Ask: "Skip posts modified in the last 2 weeks?" or "Exclude posts with comments?" One clarifying question, not a questionnaire.

3. **Show a representative preview.** If scope > 10 items, list 3–5 examples before acting. Make the impact concrete and visible.

4. **Dry-run is mandatory.** Even when `confirm_writes` is OFF, present a scope summary and wait for explicit go-ahead. This overrides the default action protocol for destructive bulk operations — no exceptions.
