What problem does it solve? Alerts fire without documented procedures, leaving 3am on-call responders to improvise fixes under stress. This Skill turns tribal knowledge and postmortem action items into executable runbooks that an engineer from another team can follow without hesitation. ## Core Features & Use Cases - Structured Procedure Authoring: Enforces a Verify → Mitigate → Diagnose → Escalate structure with explicit escalation tripwires and header blocks covering symptom, impact, severity, and last-verified date. - Observable Step Format: Every step pairs a copy-pasteable command with expected output and a what-if-not branch, and destructive actions get loud warnings with pre-checks. - Cold-Test Validation: Requires a non-author to execute the runbook in staging or a game day, treating every hesitation as a documentation defect. - Use Case: After a postmortem flags a 25-minute improvised Redis failover, write the runbook from the incident's actual commands, cold-test it with a non-expert, and cut the next failover to 6 minutes. ## Quick Start Write a runbook for the Redis failover procedure based on the commands from our last incident, including verification checks, mitigation steps, and an escalation tripwire.
