Evaluate migration plans for safe production cutover readiness.
npx skills add https://github.com/Arafly/sre-playbooks --skill migration-readiness
Please help me install this Agent Skill. Skill: migration-readiness Source: https://github.com/Arafly/sre-playbooks/tree/main/migration-readiness Command: npx skills add https://github.com/Arafly/sre-playbooks --skill migration-readiness
This Skill assesses whether a planned migration is safe to execute before any production cutover happens. It helps teams avoid hidden dependency failures, irreversible changes, weak rollback plans, and unclear ownership that can turn a migration into an outage.
Ask for a migration readiness review of your runbook and include the current state, target state, cutover steps, rollback plan, dependencies, and go/no-go criteria.
High-intent search queries and answers about installing and using this skill.
Migration safety requires evaluating scope, dependency mapping, cutover steps, and rollback plans. You must verify rehearsal evidence, observability, and decision rights to form a defensible go, conditional go, or no-go judgment before production cutover.
A go-no-go readiness review assesses whether a service, database, or platform migration is ready for execution by checking sequencing, rollback boundaries, reconciliation, and observability to prevent hidden dependency failures and outages.
Creating a rollback plan for database migration requires tracing each cutover step to identify irreversible actions and failure modes, establishing recovery boundaries, and verifying that reconciliation can safely restore the previous state.
A migration runbook for cutover rehearsal should include the current state, target state, cutover steps, rollback plan, dependency mapping, observability checks, and clear go/no-go criteria to support a readiness evaluation.
You should delay a platform or runtime migration cutover when rehearsal evidence is missing, rollback boundaries are unclear, observability is insufficient, or hidden dependency failures and irreversible changes pose outage risks.
Yes, deployment model migrations are supported alongside service, database, platform, cloud, region, runtime, and observability migrations where sequencing, rollback, and reconciliation must be verified before production cutover.
diShine-digital-agencyInventory current state and define target state for technical migrations.
yin52133Execute pre-approved workflows exactly as defined in runbooks.
kimjuyoung1127Automate Supabase MCP migrations and edge function deployments with auditable logs.
hohai99Evaluate spec compliance, test results, security posture, and rollback readiness to produce a GO/NO-GO decision and readiness report.
