monitoring-spec

Generates monitoring specifications defining metrics, alerts, dashboards, and SLOs for operations.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill monitoring-spec-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitoring-spec
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/operations/monitoring-spec
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill monitoring-spec-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship systems without a documented observability strategy, leaving alerting thresholds, SLOs, and dashboard definitions implicit and inconsistent. This Skill produces a signed, traceable monitoring specification so reliability requirements are explicit before operations begin. ## Core Features & Use Cases - Metrics Catalog Generation: Defines application, infrastructure, database, and cache metrics with types, labels, and PromQL-style SLI queries. - Alert and SLO Definitions: Produces severity-tiered alert rules, error budgets, escalation matrices, and runbook mappings. - Dashboard and Logging Specs: Specifies dashboard panels, log formats, retention policies, and distributed tracing sampling rates. - Use Case: A DevOps Lead finalizing Phase 12 (Operations) of the SDLC invokes this Skill to generate monitoring-spec.md, which is validated against nine rules and signed before the closure report can proceed. ## Quick Start Ask the agent to create the monitoring specification for your project after the infra-spec and nonfunctional-spec documents are signed.

Frequently Asked Questions about monitoring-spec

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

FAQPage Schema
How do I create a monitoring specification for my application?▼

Invoke the monitoring-spec skill after your infra-spec and nonfunctional-spec documents are signed. The agent asks for the application name, SLA target, key metrics, alert channels, and monitoring tools, then generates the full specification document.

What does a monitoring specification document include?▼

It includes SLO definitions with error budgets, a metrics catalog for application, infrastructure, database, and cache layers, severity-tiered alert rules in YAML, dashboard panel specifications, log formats and retention, and tracing sampling rates.

Which monitoring tools does the specification support?▼

The template references Prometheus for metrics, Grafana for dashboards, ELK Stack for logging, Jaeger for distributed tracing, PagerDuty for alerting, and Datadog for APM. You can substitute your own stack when answering the input questions.

What prerequisites must be signed before generating a monitoring spec?▼

Both the infra-spec document from Phase 11 and the nonfunctional-spec document from Phase 4 must exist and be signed. The skill blocks generation with a validation error if either prerequisite is unsigned.

Who approves the monitoring specification document?▼

The DevOps Lead holds final approval authority and signs the document. The Operations Lead and Solution Architect provide content reviews but their sign-off does not gate the signature.