msx:migrate

Migrate directory structures from OpenSpec or Speckit to MixSpec.

Updated Mar 16, 2026

Search Tags:#specification #migration #code migration #OpenSpec #Speckit #MixSpec

Ready to run

npx skills add https://github.com/xxyj/xx-ai-cli --skill msx-migrate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: msx:migrate
Source: https://github.com/xxyj/xx-ai-cli/tree/main/.cursor/skills/msx-16-migrate
Command: npx skills add https://github.com/xxyj/xx-ai-cli --skill msx-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @bedrock/mixspec@latest, and includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of migrating directory structures from OpenSpec or Speckit to MixSpec, ensuring a seamless transition with full directory copy and alignment of active and archived changes.

Core Features & Use Cases

Full Directory Copy: Migrate entire directories with all their contents.
Active & Archived Changes Alignment: Ensure that active and archived changes are correctly aligned during migration.
Use Case: Ideal for teams transitioning from OpenSpec or Speckit to MixSpec and looking to maintain their existing workflow without disruption.

Quick Start

Run the msx:migrate skill to start the migration process from OpenSpec or Speckit.

Frequently Asked Questions about msx:migrate

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

FAQPage Schema

How do I migrate directory structures from OpenSpec or Speckit to MixSpec?▼

To migrate directory structures from OpenSpec or Speckit to MixSpec, run the migration skill to execute a full directory copy and align active and archived changes seamlessly. This ensures your existing workflow transitions without disruption.

What is the best way to align active and archived changes during a specification migration?▼

The best way to align active and archived changes during a specification migration is to use an automated migration tool that ensures full directory copy and correct alignment of changes between OpenSpec, Speckit, and MixSpec.

Do I need @bedrock/mixspec to run OpenSpec and Speckit migrations?▼

Yes, you need the @bedrock/mixspec@latest dependency installed to execute the migration process. It provides the necessary execution environment for transitioning and aligning directories from OpenSpec or Speckit.

Can I use this specification migration tool in non-interactive environments?▼

Yes, this specification migration tool handles both interactive and non-interactive environments. You can automate the migration of your directory structures from OpenSpec or Speckit to MixSpec without requiring manual input.

Why does migrating to MixSpec require a full directory copy?▼

Migrating to MixSpec requires a full directory copy to ensure no specification files are lost during the transition. This process guarantees that both active and archived changes from OpenSpec or Speckit are perfectly aligned in the new structure.