← ClaudeAtlas

migratelisted

Migration workflow - research → analyze → plan → implement → review
parcadei/Continuous-Claude-v3 · ★ 3,791 · AI & Automation · score 83
Install: claude install-skill parcadei/Continuous-Claude-v3
# /migrate - Migration Workflow Safe migrations for frameworks, languages, and infrastructure. ## When to Use - "Migrate to X" - "Upgrade framework" - "Move from X to Y" - "Upgrade Python/Node/etc." - "Migrate database" - Framework version upgrades - Language migrations - Infrastructure changes ## Workflow Overview ``` ┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────┐ ┌───────────┐ │ oracle │───▶│ phoenix │───▶│ plan- │───▶│ kraken │───▶│ surveyor │ │ │ │ │ │ agent │ │ │ │ │ └──────────┘ └──────────┘ └────────────┘ └──────────┘ └───────────┘ Research Analyze Plan Implement Review target current migration changes migration ``` ## Agent Sequence | # | Agent | Role | Output | |---|-------|------|--------| | 1 | **oracle** | Research target framework/version | Research report | | 2 | **phoenix** | Analyze current codebase for migration impact | Impact analysis | | 3 | **plan-agent** | Create phased migration plan | Migration plan | | 4 | **kraken** | Implement migration changes | Code changes | | 5 | **surveyor** | Review migration for completeness | Migration review | ## Why Extra Gates? Migrations are high-risk: - Breaking changes between versions - Dependency conflicts - Data format changes - API deprecations The extra research and review phases catch issues early. ## Execution ### Phase 1: Research Target