evolver

Plan and execute schema, data, and API migrations with staged rollouts.

Updated Mar 26, 2026

Search Tags:#rollback #database #migrations #schema-change #data-backfill #staged-rollout

Ready to run

npx skills add https://github.com/benediktms/overmind --skill evolver-benediktms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evolver
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/evolver
Command: npx skills add https://github.com/benediktms/overmind --skill evolver-benediktms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Activates the evolver persona to manage high-stakes migrations—schemas, data backfills, breaking API changes, and dependency upgrades—with reversibility-first discipline, staged rollouts, and idempotent, batched backfills.

Core Features & Use Cases

Enforces a documented rollback for every change and staged rollout to minimize risk.
Guides end-to-end migration tasks from planning to handoff, including pre-claim ownership checks and post-deploy monitoring.
Applies to production migrations that require careful sequencing, backward-compatibility planning, and controlled feature flags.

Quick Start

Initiate a migration with a rollback, staged rollout plan, and idempotent backfills.

Frequently Asked Questions about evolver

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

FAQPage Schema

How do I plan a database schema migration with zero downtime and a safe rollback?▼

Database schema migration with zero downtime requires a documented rollback plan, staged rollout, and forward-then-backward compatibility to minimize data loss. You can enforce reversibility-first discipline by applying chunked, idempotent backfills before completing the deploy.

What is the best way to execute data backfills during a production migration?▼

Data backfills during production migration should be executed in idempotent, batched chunks to minimize risk. Running staged rollouts ensures the backfill remains traceable and reversible, preventing locking issues and data inconsistency across your services.

Can I use evolver for breaking API changes and dependency upgrades across production services?▼

Yes, evolver applies to breaking API changes and dependency upgrades across production services by enforcing staged rollouts and controlled feature flags. It guides end-to-end migration from planning to handoff with pre-claim ownership checks and post-deploy monitoring.

How does staged rollout work for high-stakes database migrations?▼

Staged rollout for high-stakes database migrations works by sequencing schema changes and data backfills incrementally. This approach requires forward-then-backward compatibility and a documented rollback for every change, ensuring minimal downtime and data loss during deployment.

When do I need forward and backward compatibility for schema changes?▼

Forward and backward compatibility is needed for schema changes whenever you require a reversible migration path without downtime. It allows production services to handle requests safely during a staged rollout, ensuring that rolling back does not break application logic.

What are the limitations of using automated schema migrations for large-scale production systems?▼

Automated schema migrations without a documented rollback plan risk data loss and extended downtime during large-scale production systems. Limitations arise from unmonitored backfills and breaking API changes, requiring traceable ownership and staged rollouts to mitigate failures.