What problem does it solve? Once software ships, teams often lack a structured way to keep it healthy: monitoring is ad hoc, incidents depend on one person's memory, and lessons from production never make it back into the lifecycle. This Skill provides a disciplined operations phase covering observability, incident management, runbooks, and continuity. ## Core Features & Use Cases - Observability and SLOs: Set up logs, metrics, and traces with SLOs that define "healthy" and alerts that fire before users notice. - Incident Management: Detect, triage by impact, mitigate, resolve, and write blameless postmortems, with every incident yielding a prevention item. - Runbooks and Continuity: Document procedures for routine operations and recovery paths, and verify backup, failover, and rollback through actual testing. - Use Case: After deploying a new service, use this Skill to define SLOs, wire up alerting, write rollback runbooks, and route recurring toil back to maintenance and new needs to requirements-gathering. ## Quick Start Use the operations skill to define SLOs, alerting, and an incident response runbook for our newly deployed payment service.
