hypercare-exit-criteria

Define exit criteria by setting measurable thresholds across five categories: system stability, operational readiness, process maturity, documentation completeness, and business confidence. Each criterion should require sustained achievement, such as 99.9% availability for two consecutive weeks, plus stakeholder sign-off.

Include availability, error rate, latency percentiles (P50, P95, P99), throughput, incident frequency by severity, and resource utilization (CPU, memory, database connections, disk). Each metric needs a concrete target and a minimum sustained duration before transition.

The Skill requires the hypercare monitoring setup, incident response procedures, performance validation plan, knowledge transfer plan, and the optimization report with performance baselines. Business requirements like acceptable risk levels and SLA commitments are also needed.

The Skill defines a contingency plan with three options: extend hypercare and re-evaluate weekly, perform a partial transition with extended engineering backup, or consider rollback if stability cannot be achieved. The decision requires engineering, operations, and executive approval.

Approval is required from the Engineering Manager, Operations Lead, Product Owner, and the CTO for final sign-off. The Skill provides a sign-off template capturing technical approval, business approval, and transition authorization with conditions.