ops-monitoring

Generate an operational monitoring design document with CloudWatch alarms and Slack templates.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/KazusaNakagawa/claude_docs --skill ops-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-monitoring
Source: https://github.com/KazusaNakagawa/claude_docs/tree/main/skills/ops-monitoring
Command: npx skills add https://github.com/KazusaNakagawa/claude_docs --skill ops-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates a production-ready operational monitoring design document (09.ops-monitoring.md) for AWS CloudWatch + Slack notification workflows by analyzing input designs (08.job-api-design.md and 04.detail-design.md), covering daily health checks, DLQ monitoring, SLO validation, incident response flows, and Slack notification templates.

Core Features & Use Cases

  • Convert design inputs into a comprehensive ops design with CloudWatch alarms, SNS/Slack integration, and ready-to-use templates.
  • Produce step-by-step runbooks including daily health checks, DLQ handling, and SLO verification to support production readiness.
  • Reuse existing design docs to output a unified 09.ops-monitoring.md that teams can publish as part of incident readiness packages.

Quick Start

Feed 08.job-api-design.md and 04.detail-design.md to generate the complete 09.ops-monitoring.md ready for production incident readiness.

Frequently Asked Questions about ops-monitoring

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

FAQPage Schema
How do I generate a CloudWatch monitoring design with Slack notifications from existing design documents?

To generate a CloudWatch monitoring design with Slack notifications, feed your existing job API and detail design markdown files into the automation. It analyzes the inputs to produce a consolidated ops monitoring document with defined alarms, channels, and runbooks.

What is needed to set up DLQ monitoring and SLO verification runbooks for AWS?

Setting up DLQ monitoring and SLO verification runbooks for AWS requires input design documents like job API and detail designs. The tool processes these inputs to output step-by-step runbooks covering daily health checks and incident response flows.

Can I automate operational monitoring design for production readiness using existing markdown files?

Yes, you can automate operational monitoring design by providing your existing markdown design documents. It converts these design inputs into a comprehensive ops design with CloudWatch alarms, SNS integration, and ready-to-use Slack notification templates.

Does this approach work for creating incident readiness packages with SNS and Slack integration?

Yes, this approach works for creating incident readiness packages by generating a unified operational monitoring design document. It includes SNS and Slack integration templates, DLQ handling, and SLO validation to support production readiness.

Why do I need to provide detail design and job API documents to generate an ops monitoring strategy?

You need to provide detail design and job API documents because the operational monitoring strategy is derived directly from these inputs. Analyzing them ensures the generated CloudWatch alarms, runbooks, and Slack workflows accurately reflect your specific architecture.