on-call-design

Design on-call rotations, escalation tiers, runbooks, and compensation models.

7|Updated Mar 19, 2026

Search Tags:#runbook #on-call #escalation #rotation #sla #burnout #pagerduty

One-click install

npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill on-call-design

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: on-call-design
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/on-call-design
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill on-call-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams struggle with inconsistent on-call rotations, noisy alerts, unclear escalation, and burnout; this skill provides a repeatable framework to design rotations, escalation tiers, runbooks, and compensation to improve response time and engineer wellbeing.

Core Features & Use Cases

Rotation patterns: Recommended schedules (weekly, follow-the-sun, primary/secondary, hybrid) and a suggested weekly primary/secondary pattern with handoff rules.
Escalation policies: Step-based escalation with SLA timeouts and notification targets to model PagerDuty/OpsGenie-style flows.
Runbook standards: Required runbook contents including service overview, health checks, common failure modes, contact lists, and escalation criteria.
Compensation & fairness: Options for pay, comp time, reduced load, and metrics to track parity and burnout (pages per person, MTTA, satisfaction).
Quality gates & mitigation: Checklist for coverage, noise thresholds, automation criteria for recurring pages, and blameless postmortems.

Quick Start

Create an on-call plan for a production service that defines a weekly primary/secondary rotation, escalation SLAs, required runbook sections, and a compensation approach to prevent burnout.

Frequently Asked Questions about on-call-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a fair on-call rotation to prevent engineer burnout?▼

Establish on-call escalation policies by creating step-based escalation flows with defined SLA timeouts and specific notification targets to model PagerDuty or OpsGenie-style incident response workflows.

What should be included in production service runbook standards?▼

Required runbook standards include a service overview, health checks, common failure modes, contact lists, and escalation criteria to ensure engineers can respond to production incidents effectively.

What is the best way to structure on-call schedules for global engineering teams?▼

Track on-call fairness by monitoring metrics such as pages per person, mean time to acknowledge (MTTA), and engineer satisfaction to identify workload imbalances and mitigate burnout across the team.

When should I automate recurring on-call pages instead of escalating them?▼

You should automate recurring on-call pages when they meet noise threshold criteria, shifting from manual incident escalation to automated remediation to reduce alert fatigue and improve response quality.