{"id":77014,"plugin_id":"plugins_6ab41ed5b8c4819199eb5bbf91ce25f5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:18.879Z","digest":"73f63c46b7bde6859f5c125c08fc7c8e71ae4dfefa042b681a7829142a5e61e9","against":null,"payload":{"description":"Change API contracts, serialized formats, events or database schemas using compatible rollout and data-migration strategies.","included_files":[],"name":"migrate-interfaces-and-schemas","skill_md_contents":"---\nname: migrate-interfaces-and-schemas\ndescription: Change API contracts, serialized formats, events or database schemas using compatible rollout and data-migration strategies.\n---\n\n# Migrate Interfaces And Schemas\n\nUse this skill only for its stated purpose. Follow the shared source-of-truth, permission and evidence rules in `../../references/workflow-contract.md`. Read `../../references/migration-safety.md` for detailed method when necessary.\n\n## Procedure\n1. Inventory producers, consumers, retained data and backward-compatibility commitments.\n2. Choose expand/contract or versioned contract strategy, with validation and defaults.\n3. Plan safe migration order, dual-compatibility period, idempotent backfills and restore strategy.\n4. Test both old and new consumers and failure/rollback cases when possible.\n5. Obtain approval for destructive steps, broad backfills or production writes.\nDeliver migrations and tests with explicit compatibility risks.\n\n## Handoff rule\nState actual artifacts or grounded code findings and validation status. Never invent file paths, executed tests, tool access, or completed subagent work. Keep output proportionate to the user request.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}