# Review Operational Readiness

> Reviews operational readiness when asked who will support a service or whether alerts, capacity, recovery, and runbooks are sufficient; reports gaps without deploying it.

- Skill: `jovanipink/review-operational-readiness` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add jovanipink/review-operational-readiness`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/review-operational-readiness/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jovanipink/review-operational-readiness

---


# Operational Readiness Review

Use [Google SRE monitoring guidance](https://sre.google/sre-book/monitoring-distributed-systems/) for signal and alerting concepts. The broader ownership, recovery, and readiness checks below are this catalog's review contract; they require separate system evidence.

## Workflow

1. Define critical journeys, service objectives, owners, support hours, dependencies, and failure budgets.
2. Review deployment, configuration, capacity, rate limits, queues, retries, timeouts, backpressure, and graceful degradation.
3. Assess logs, metrics, traces, dashboards, symptom-based alerts, escalation, and runbook actionability.
4. Review backup, restore, disaster recovery, regional or dependency failure, and data reconciliation evidence.
5. Inspect incident roles, communication paths, severity rules, status updates, and learning processes.
6. Verify rollback, feature control, canary, deploy markers, and post-release observation plans.
7. Classify each readiness item as proven, partial, blocked, or not applicable with evidence.

## Boundaries

- Do not infer live readiness from a local build or passing repository checks.
- Do not claim backup recovery without an observed restore test.
- Do not deploy, page responders, change provider settings, or declare go without separate authority.

## Output

Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.

Return Objectives and ownership, Failure readiness, Observability, Recovery, Incident response, Blockers, and Go or no-go decision needs.

## Example

Synthetic example; not an observed client result.

Input: A service has alerts but no on-call owner or recovery procedure.

Output: Readiness is incomplete: alerts lack an accountable responder and tested recovery path. Name both gaps before release approval.

