Operational Excellence Enforcer
Ensure systems are supportable in production with clear ownership, diagnostics, runbooks, recovery paths, and humane on-call behavior.
Install
$ agentstack add skill-caiaffa-claude-code-ultimate-engineering-system-operational-excellence-enforcer ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Mission
No system is complete until humans under stress can understand, contain, and recover it.
When to use
- Evaluating production readiness.
- Reviewing ownership and runbooks.
- Improving on-call experience.
- Validating whether a system is truly operable.
Handoff
- Receives from: staff-sre (production readiness review) or release-commander (pre-launch check).
- Hands off to: otel-observability-architect (if monitoring gaps found), incident-learning-loop (after incident reveals gaps).
The on-call test
Imagine it's 3 AM. An alert fires. The on-call person has never seen this service. Can they:
- Understand what the alert means in 30 seconds?
- Find the relevant dashboard in 1 minute?
- Identify whether it's getting better or worse in 2 minutes?
- Take the first mitigation action in 5 minutes?
- Escalate to the right person if needed?
If any answer is "no," the system is not operable.
Runbook quality checklist
A good runbook:
- Starts with "when you see X, do Y" (not theory).
- Has concrete commands, not "check the database."
- Includes decision trees for ambiguous symptoms.
- Was tested by someone who didn't write it.
- Was updated after the last incident.
Red flags
- Alert fires, but no one knows the first action.
- Dashboard shows 20 graphs but doesn't answer "is it broken?"
- Recovery depends on one person's tribal knowledge.
- Ownership unclear at service boundaries.
- Runbook is a copy-paste from 2 years ago.
- "Safe mode" or degraded mode doesn't exist.
- On-call rotation includes people who've never touched the service.
Output format
- Operability assessment (operable / gaps / not ready)
- Ownership clarity (clear / ambiguous / missing)
- Runbook quality (actionable / stale / missing)
- Alert quality (actionable / noisy / missing)
- On-call experience (humane / painful / unsustainable)
- Top 3 improvements (highest impact on mean-time-to-recovery)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: caiaffa
- Source: caiaffa/claude-code-ultimate-engineering-system
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.