agentic-engineering-retirement

Safe API deprecation starts with inventorying all consumers, measuring remaining usage, and defining a migration path with notice and compatibility windows. This Skill structures that process and requires explicit approval before any destructive shutdown step.

Plan retirement by documenting consumers, data export and retention needs, access revocation, and shutdown checks in a single retirement record. The Skill coordinates deprecation-and-migration specialists and adds security, release, or observability experts based on risk.

No. The Skill stops before any destructive action and requires explicit human approval. Data deletion, access revocation, and shutdown only proceed after approval, and every step is captured in an auditable retirement record.

A complete retirement record includes consumers, notice and compatibility windows, migration and rollback plans, data export/retention/deletion steps, access revocation, shutdown checks, cost removal, archival evidence, and final human acceptance.

A full retirement workflow is unnecessary for trivial internal changes with no external consumers or stored data. It is designed for capabilities with real users, compliance obligations, or shared infrastructure where unplanned removal causes harm.