skills.rest
chaletteholdings
chaletteholdingsCOMMUNITY
Explore all skills by this author →
GitHub

migration-v2

Route legacy migration triggers to command-room-onboarding Phase 1.5 with a deprecation notice.

Updated Aug 27, 2026
Search Tags:#onboarding#compatibility#migration#deprecation#legacy#tombstone#workspace-ingest
One-click install
npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill migration-v2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-v2
Source: https://github.com/chaletteholdings/command-room-releases-2710/tree/main/command-room/skills/migration-v2
Command: npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill migration-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routes legacy migration triggers to the modern onboarding flow and provides a clear deprecation notice.

Core Features & Use Cases

  • Tombstone for legacy triggers: returns a deprecation notice and redirects to command-room-onboarding Phase 1.5.
  • Back-compat routing: forwards upgrade/in-place triggers to the new workspace-ingest workflow.
  • Safe exit: does nothing else if the user declines upgrade.

Quick Start

Initiate the on-boarding upgrade flow using workspace-ingest via Phase 1.5 to migrate legacy data.

Frequently Asked Questions about migration-v2

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

FAQPage Schema
How do I route legacy migration triggers to the modern onboarding flow?▼

Legacy migration triggers are routed to the modern onboarding flow by forwarding them to command-room-onboarding Phase 1.5, which presents a deprecation notice and guides the upgrade path.

What happens to deprecated back-compat triggers during a data migration?▼

Deprecated back-compat triggers return a tombstone deprecation notice and redirect upgrade or in-place triggers to the workspace-ingest workflow for data migration.

Does this migration tombstone perform the data migration itself?▼

No, the migration tombstone does not perform data migration itself; it solely serves as a back-compat routing guide that forwards triggers to workspace-ingest for the actual migration.

What is the correct upgrade path for migrating legacy data?▼

The correct upgrade path for migrating legacy data initiates the onboarding upgrade flow via command-room-onboarding Phase 1.5, ultimately forwarding to workspace-ingest for data migration.

What happens if I decline the legacy upgrade during the onboarding flow?▼

If you decline the legacy upgrade during the onboarding flow, the routing provides a safe exit and does nothing else, leaving your current setup unchanged.

When do I need a tombstone for back-compat triggers?▼

You need a tombstone for back-compat triggers when you want to safely deprecate legacy migration paths and redirect users to the modern onboarding flow without breaking existing integrations.

Related Skills

Explore More Software Engineering Skills→
diegosanchespereira1diegosanchespereira1

bmad-create-prd

Create product requirements documents from conversation context and project customization.

Community
Intermediate
tteamtmtteamtm
8

dbcli-export

Export table data to SQL INSERT scripts for backups.

Community
Intermediate
BillChiricoBillChirico
1

onboarding-cro

Define activation goals and design one-goal onboarding flows for SaaS products.

Community
Advanced
hyndanielhyndaniel
10

数据快推

Post ledger and report data changes to board ingest APIs via Python script.

Community
Intermediate