Results for “migration-strategy”

Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases.

Terceiro agente do Time de Migração. Propõe estratégias de migração com trade-offs explícitos, considerando brief, paradigma e apetite. Recomenda uma estratégia mas deixa a escolha como decisão humana. Produz migration_strategy.md, risk_register.md e cutover_plan.md. Ativação: /reversa-strategist (geralmente invocado por /reversa-migrate).

Migration Architect

Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, a host installer, or a community package), when a user wants to draft a migration plan, when an agent needs to reason about pending migrations, or when working through an in-progress migration.

Plans framework, API, schema, service, package, UI, build, or infrastructure migrations with slices, rollback, and validation.

Migration Architect

Use when schema or data migrations need safe rollout and rollback planning.

Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

Provides safe, reversible database schema change patterns for PostgreSQL, MySQL, and common ORMs, with guidance on zero-downtime deployments, rollbacks, and migration tooling.

Cloud Migration Architect

Plan and execute migrations from Zscaler, Palo Alto, legacy VPN, or SASE stacks to Cloudflare One with policy mapping, rollout plans, and parity analysis.

Apply design, canon, and modules to every page in the inventory to produce a deployable static HTML site. Per-page, incremental, and idempotent.

Migrates legacy AEM (6.x, AMS, on-prem) to AEM as a Cloud Service using BPA CSV or CAM/MCP target discovery, with one-pattern-per-session workflow for scheduler, replication, event listener, HTL lint, dialog, and custom widget migration.

Migrate Pester v5 classic Should -Be assertion syntax to the new Pester v6 Should-* operators with a step-by-step mapping and behavioral gotchas.

Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan.

Orchestrates the full-site migration preparation cascade — inventory crawl, page-type and module catalog confirmation, archetype prototyping, and asset preparation — with confirmation gates between phases.

Create, execute, and roll back versioned database schema migrations using tools like Alembic, Prisma Migrate, Flyway, and Knex. Use when the user requests database migration or provides relevant inputs for this workflow.

Plan and execute safe Convex schema and data migrations using the widen-migrate-narrow pattern and the @convex-dev/migrations component.

Safe patterns for evolving database schemas in production with decision trees and troubleshooting guidance.

International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.

Databricks → Fabric migration assessment + execute

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

Prisma ORM expert for schema design, migrations, query optimization, relations modeling, and database operations. Use PROACTIVELY for Prisma schema issues, migration problems, query performance, relation design, or database connection issues.

Implement data access patterns, Scaling, Migrations, and ORM selection in NestJS. Use when implementing TypeORM/Prisma repositories, migrations, or database patterns in NestJS.

Use this when reviewing database, storage, config, queue, or integration migrations for rollout safety, rollback feasibility, data correctness, and environment-specific deployment risk.

`analysis-agent`/`task-agent`/`review-agent`: use when migration, backfill, deployment order, rollback, or live-data safety needs design; skip when no data migration exists.

Agent profile for lead framework, dependency, database, SDK, and architecture migrations with sequencing and rollback. Use when Codex needs a specialist agent perspective for planning, implementation, review, debugging, validation, or handoff in this domain.

Upgrades PowerShell Pester test suites across major versions (v3→v4, v4→v5, v5→v6) with structured workflows, reference guides, and safety rules.

Migrate Claude Code configuration, skills, agents, and MCP servers to Codex project and global files.

Design JWT strategies with refresh tokens. TRIGGERS - Use when user needs help with jwt-strategy related tasks.

Imported skill composite from langchain

Harness Strategy

The relevant axis is not "how do we deploy" but "how fast and how cheaply can we