skills.rest
Corvalis-LLC
Corvalis-LLCOFFICIAL
Explore all skills by this author →
GitHub

auto-evolution

Coordinate schema and API evolution with phased migrations and dual-writing.

6|Updated Mar 31, 2026
Search Tags:#deployment#api#schema#migration#deprecation#evolution#backward-compatibility
One-click install
npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill auto-evolution-corvalis-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-evolution
Source: https://github.com/Corvalis-LLC/Crow-Stack/tree/main/skills/auto-evolution
Command: npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill auto-evolution-corvalis-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Schema and API evolution is challenging in live systems; this discipline ensures backwards-compatible changes, safe rolling deploys, transition periods, and deprecation paths to minimize disruption.

Core Features & Use Cases

  • Enforces Expand, Migrate, Contract phases to safely introduce changes without breaking existing consumers.
  • Supports rolling deployments, dual-writing, and deprecated field handling to coordinate updates across distributed components.
  • Use case: updating a shared API or data contract with a staged rollout that keeps old clients functional while new ones are introduced and old fields are phased out.

Quick Start

Plan your change with a migration strategy that preserves compatibility for all consumers during rollout.

Frequently Asked Questions about auto-evolution

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

FAQPage Schema
How do I ensure backward compatibility when updating an API contract?▼

Backward compatibility during API evolution is maintained by applying Expand, Migrate, Contract phases. This staged rollout approach introduces changes gradually, keeping old clients functional while new consumers are updated and deprecated fields are safely phased out.

What is the best way to handle database schema migration during rolling deployments?▼

Safe database schema migration during rolling deploys requires dual-writing and runtime defaults. This ensures both old and new application versions remain functional, preventing breaking changes while the shared data structures evolve across distributed components.

When do I need to use the Expand, Migrate, Contract pattern for schema evolution?▼

The Expand, Migrate, Contract pattern is needed when updating shared API contracts or config formats in live systems. It coordinates transition periods and deprecation paths, preventing disruption to existing consumers during gradual migrations across evolving software stacks.

Can I use dual-writing to prevent breaking changes in distributed components?▼

Yes, dual-writing prevents breaking changes in distributed components by writing to both old and new schemas simultaneously. This compatibility requirement ensures rolling deployments remain functional for all consumers during the migration and deprecation lifecycle.

How do I safely deprecate fields in a shared data structure without breaking old clients?▼

Safely deprecating fields in a shared data structure requires a phased migration strategy with transition periods. By enforcing runtime defaults and handling deprecated fields gradually, old clients remain functional while new consumers transition to the updated formats.

Related Skills

Explore More Software Engineering Skills→
LazyIsEfficientLazyIsEfficient
15

api-and-interface-design

Define typed API contracts with consistent error semantics and boundary validation.

Official
Advanced
softsparksoftspark
161

migration-patterns

Plan and execute safe database migrations for live web apps.

Community
Advanced
heaptracetechnologyheaptracetechnology
13

contract-test

Automate API contract testing with schema validation and OpenAPI checks.

Community
Advanced
aquariuscookaquariuscook

contract-testing

Automate consumer-driven contract testing for microservices using Pact and schema validation.

Community
Advanced