What problem does it solve?
This Skill helps teams treat service launches, handovers, sunsets, and shutdowns as formal engineering workflows instead of informal events. It reduces the risk of unclear ownership, incomplete cutovers, zombie services, forgotten dependencies, and unsafe retirements.
Core Features & Use Cases
- Structured launch planning: Defines system boundaries, acceptance criteria, factory-style and site-style testing, punchlists, and sign-off requirements for bringing a new service into production.
- Safe retirement workflows: Guides decommissioning through traffic draining, credential lockout, zero-energy verification, and explicit asset disposition for code, data, infrastructure, DNS, and monitoring.
- Mothball vs. demolish decisions: Helps decide whether a system should be preserved for possible restart or fully removed, with documentation of restoration assumptions and retained artifacts.
- Use case: When retiring an old internal API after migrating clients to a replacement, use this Skill to announce deprecation, stop new traffic, drain remaining consumers, revoke secrets, archive the repo, and record what was preserved or deleted.
Quick Start
Ask the commissioning-and-decommissioning skill to create a decommissioning plan for a service you are retiring, including drain steps, lockout actions, zero-energy checks, and asset disposition decisions.
