production-readiness

What problem does it solve? Teams often mark a feature as done when tests pass, only to discover in production that nobody owns it, nothing is monitored, and no one knows what to do when it breaks. This Skill blocks that gap by auditing every change against a strict operational readiness checklist before release. ## Core Features & Use Cases - Blocking Readiness Checklist: Verifies eight non-negotiable items: owner, structured logs, metric, actionable alert, SLO, runbook, tested rollback, and dependency failure handling. - Evidence-Based Audit: Reads the actual diff and instrumentation instead of assuming coverage, and reports concrete missing items such as a specific metric that must be added. - Release Gate Integration: Feeds its findings into the release dossier and blocks the release when any item is uncovered, delegating observability details to the /observe skill and the sre-engineer agent. - Use Case: Before shipping a new payment endpoint, run the audit to confirm an on-call owner exists, error paths emit structured logs, a latency SLO is measured, and a rollback path has been tested. ## Quick Start Run /production-readiness on my current change to audit whether it is truly ready for production.