loom-deprecation-and-migrationlisted

# loom-deprecation-and-migration Deprecation and migration is a multi-surface playbook for safe removal and replacement. It decides whether change is warranted, specifies the target contract, plans the migration, executes bounded slices, proves adoption, audits risk, and cleans up. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-research`, `loom-specs`, `loom-plans`, `loom-tickets`, `loom-evidence`, `loom-audit`, `loom-constitution`, `loom-knowledge`, and `loom-retrospective`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. ## Use This Playbook When Use this playbook when: - replacing a system, API, library, data shape, workflow, or feature - sunsetting a feature or old path - consolidating duplicate implementations - removing dead or zombie code - migrating users, data, integrations, records, or configuration - deciding whether to maintain legacy behavior or invest in migration ## Route Use this route: ```text decide -> specify -> plan -> migrate -> prove -> remove -> prevent ``` ## Decide Start with research when the decision is not obvious. Answer: - what unique value the old system still provides - current consumers and usage - replacement readiness - migration cost for each consumer - ongoing maintenance cost and risk - compatibility obligations - security, policy, or user impact - whether removal is advisory or compulsory Route dur