bmad-observability-readiness

Generate observability plans, instrumentation tasks, and SLO dashboard specifications.

67|11|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/bacoco/BMad-Skills --skill bmad-observability-readiness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-observability-readiness
Source: https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/bmad-observability-readiness
Command: npx skills add https://github.com/bacoco/BMad-Skills --skill bmad-observability-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and scripts (resource) components.

What problem does it solve?

This skill defines observability foundations including instrumentation, dashboards, and alerting plans.

Core Features & Use Cases

  • Observability plan and backlog.
  • Instrumentation tasks and SLO dashboard specs.
  • Runbooks and alerts.

Quick Start

Mention "add logging" or "observability gaps" to generate the observability artifacts.

Frequently Asked Questions about bmad-observability-readiness

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

FAQPage Schema
How do I set up observability foundations for my system?

Observability foundations establish instrumentation, metrics, and alerting across your system. This Skill creates an observability plan, instrumentation tasks, SLO dashboards, and runbooks by defining logging, metrics, traces, and alerts tailored to your environment's end-to-end telemetry needs.

What's included in an observability backlog and dashboard specification?

An observability backlog prioritizes instrumentation, metrics cataloging, structured logging, and tracing work. Dashboard specifications detail SLO/SLI definitions, alert thresholds, and visualization layout to enable SLO-driven reliability monitoring across development and production.

How do I implement OpenTelemetry tracing and structured logging?

Structured logging and OpenTelemetry tracing capture detailed telemetry across your stack. This Skill generates instrumentation design tasks, metrics definitions, and tracing configuration guidance to establish consistent, queryable observability signals.

Can I use this for both development and production environments?

Yes. This Skill designs end-to-end telemetry coverage applicable to both development and production, including logging, metrics, traces, dashboards, and alerting configured for each environment's reliability and debugging needs.

What's the difference between metrics, logs, and traces in observability?

Metrics measure quantitative system behavior; logs capture discrete events; traces track request flow across services. This Skill establishes all three as interconnected foundations, defining which to collect, how to structure them, and how to correlate them for SLO tracking.

How do I define SLOs and SLIs for alerting?

SLO/SLI definitions establish reliability targets and measurable indicators. This Skill generates SLO dashboard specifications and alert runbooks that translate SLIs into actionable thresholds, enabling alert rules tied to your service's promised availability.