What problem does it solve? Retiring software assets is risky: hidden consumers break, derived data keeps answering queries after the source is gone, and irreversible deletions happen without proof. This Skill structures retirement so removal only happens after live usage is proven zero and the irreversible step is separated from the decision. ## Core Features & Use Cases - Removal Proof: Requires live telemetry over the real usage cycle, dependency search, and identification of the slowest consumer before any deletion. - Reverse Contraction Sequence: Structures retirement as deprecate, switch reads, stop writes, observe cold, then drop, with every intermediate step runnable and reversible. - Decision/Act Separation: Splits the deletion decision (manifest, dry-run, review, four-eyes approval) from the irreversible delete act. - Use Case: When decommissioning a legacy API, use this Skill to produce a removal proof from telemetry, plan a Sunset/deprecation window, tombstone old consumers, and delete code, config, flags, docs, and dashboards together with a resurrection guard. ## Quick Start Use the structural-retirement skill to plan the safe deprecation and deletion of our legacy reporting API and its derived tables.
