oc-monitoring-ops

Topics in the source

• Monitoring Ops
• /oc-monitor — Command Reference
• Session Persistence (Checkpoint Protocol)
• Resume on Start
• What's Tracked
• How This Skill Fits the Pipeline
• Cross-Skill Connections
• Observability Maturity Model

On first invocation, read references/orchestrator.md and follow its welcome protocol. Post-deployment observability skill. Deploy-ops ships the code; oc-monitoring-ops watches it run. Covers five domains: uptime monitoring, error tracking, structured logging, alerting pipelines, and incident response. This skill does NOT build features or deploy code — it instruments what's already deployed and establishes the feedback loop that catches problems before users report them. -- Checkpoint: {project-dir}/.checkpoints/oc-monitoring-ops.checkpoint.json When any /oc-monitor command is invoked: 1. Check for checkpoint 2. If exists: show tier, tools, SLO status, active incidents, maturity grade, next action 3. Ask: "Continue, restart, or show full checkpoint?" 4. On continue: load context, resume from nextactions[0] Monitoring-ops uniquely stores runtime state alongside pipeline progress — the last health check result, active incident count, and SLO budget consumption. This means the checkpoint serves double duty: session persistence AND operational snapshot. -- oc-deploy-ops ships it, oc-monitoring-ops watches it. The handoff: 1. oc-deploy-ops completes production promotion 2. oc-deploy-ops

This is an excerpt. Refer to the complete source and its current requirements.