migrate-workspace

Name: migrate-workspace
Availability: InStock
Author: largo2z9

Migrate brand workspaces to newer template versions while preserving data.

1|Updated Apr 20, 2026

Search Tags:#schema migration #data preservation #brand management #workspace migration #version synchronization #template upgrade

Ready to run

npx skills add https://github.com/Largo2z9/phantomos --skill migrate-workspace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migrate-workspace
Source: https://github.com/Largo2z9/phantomos/tree/main/.skills/skills/migrate-workspace
Command: npx skills add https://github.com/Largo2z9/phantomos --skill migrate-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents workspace drift by safely updating existing brand instances to match newer template versions without losing operator data or introducing uncontrolled structural changes.

Core Features & Use Cases

Template Version Comparison: Detects version gaps and analyzes differences between brand resources and target templates.
Safe Migration Planning: Proposes additions, renames, restructuring, and deprecations with operator review before execution.
Use Case: When a DTC brand workspace has fallen behind a template release, use this Skill to generate a migration plan, preserve existing information, and bring resources back into alignment.

Quick Start

Ask the migrate-workspace skill to upgrade the brand workspace to the latest template version while preserving existing data.

Frequently Asked Questions about migrate-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I upgrade a brand workspace to a new template version without losing data?▼

To upgrade a brand workspace without data loss, perform a template version comparison to detect structural diffs, generate a safe migration plan for operator review, and execute rollback-safe transformations. This preserves existing data while aligning resources with the new template.

What is the best way to resolve template version mismatches in brand management?▼

Resolving template version mismatches involves controlled resource synchronization to prevent workspace drift. You analyze differences between brand resources and target templates, propose additions or renames, and apply validated structural updates to bring the workspace back into alignment.

Can I review structural changes before applying a workspace migration?▼

Yes, safe migration planning requires operator review before execution. The process proposes additions, renames, restructuring, and deprecations based on structural diffs, ensuring uncontrolled changes are prevented and you maintain full control over the workspace transformation.

Does workspace migration support rollback for destructive updates?▼

Workspace migration prevents destructive updates through rollback-safe transformations and validation checks. By requiring backups and version comparison before execution, the process ensures workspace integrity and allows recovery if the template synchronization fails.

When do I need to run a schema migration for brand operations?▼

You need schema migration for brand operations when a DTC brand workspace has fallen behind a template release. This version gap causes workspace drift, requiring controlled resource synchronization to safely align brand instances with newer template structures.