superpowers-sage:migrating

What problem does it solve?

WordPress sites often need risky data-changing migrations (content, postmeta, terms, attachments, and legacy plugin structure), and teams need a reliable way to migrate without losing data or ending up with a non-revertible mess.

Core Features & Use Cases

• 7-phase, safety-harness migration contract: snapshot-before, dry-run compute, human approval gate, preflight checks, apply with row-level logging, snapshot-after verification, and idempotency proof.
• Destructive-first is forbidden: it enforces snapshot-before and blocks autonomous apply until you explicitly approve the dry-run diff.
• Common WordPress migration scenarios: post_content rewrites (shortcodes to Blade, markup updates), postmeta cleanup, term taxonomy fixes, attachment regeneration, user role migration, and bulk option updates (including serialized data).
• Sage/Acorn-specific migration intent: guides safe reversible moves toward Bedrock wp-content structure and modern Roots service provider / Composer-style patterns, including legacy plugin-to-Acorn migrations.

Quick Start

Instruct your AI assistant to run: “Use superpowers-sage:migrating to migrate classic theme data safely with snapshot-before, dry-run diff, and only apply after I approve; start with migration name ‘my-migration’ and target scope ‘pages+postmeta’.”