BMAD Observability Readiness Skill
When to Invoke
Use this skill when the user:
- Mentions missing or low-quality logging, metrics, or tracing.
- Requests monitoring/alerting setup before a launch or major release.
- Needs SLOs, dashboards, or on-call runbooks.
- Reports alert fatigue or noise that needs rationalization.
- Wants to ensure performance and reliability work has data coverage.
If instrumentation already exists and only specific bug fixes are required, hand over to bmad-development-execution with the backlog produced here.
Mission
Deliver a comprehensive observability plan that enables diagnosis, alerting, and measurement across the system. Ensure downstream performance, reliability, and security work has trustworthy telemetry.
Inputs Required
- Architecture diagrams and component inventory.
- Existing logging/monitoring/tracing configuration (if any).
- Current incidents, outages, or blind spots experienced by the team.
- SLAs/SLOs, business KPIs, or compliance reporting requirements.
Outputs
- Observability plan detailing metrics, logs, traces, dashboards, and retention policies.
- Instrumentation backlog with implementation tasks, owners, and acceptance criteria.
- SLO dashboard specification covering golden signals, alert thresholds, and runbook links.
- Updated runbook or escalation paths if gaps were discovered.
Process
- Audit current telemetry coverage, tooling, and data retention. Document gaps.
- Define observability objectives aligned with user journeys and business KPIs.
- Design instrumentation strategy: metrics taxonomy, structured logging, trace spans, event schemas.
- Establish SLOs, SLIs, and alerting strategy with on-call expectations and noise controls.
- Produce dashboards/reporting requirements and data governance notes.
- Create backlog with prioritized instrumentation tasks and verification approach.
Quality Gates
- Every critical user journey has metrics and alerts defined (latency, errors, saturation, traffic).
- Logging standards specify structure, PII handling, and retention.
- Alert runbooks documented or flagged for creation.
- Observability plan references integration with performance, security, and incident workflows.
Error Handling
- If telemetry tooling is undecided, present comparative options with trade-offs.
- Highlight dependencies on platform teams or infrastructure before finalizing timeline.
- Escalate when observability requirements conflict with compliance or privacy constraints.
1---2name: bmad-observability-readiness3description: Establishes instrumentation, monitoring, and alerting foundations.4---5
6# BMAD Observability Readiness Skill
7
8## When to Invoke
9
10Use this skill when the user:
11- Mentions missing or low-quality logging, metrics, or tracing.
12- Requests monitoring/alerting setup before a launch or major release.
13- Needs SLOs, dashboards, or on-call runbooks.
14- Reports alert fatigue or noise that needs rationalization.
15- Wants to ensure performance and reliability work has data coverage.
16
17If instrumentation already exists and only specific bug fixes are required, hand over to `bmad-development-execution` with the backlog produced here.
18
19## Mission
20
21Deliver a comprehensive observability plan that enables diagnosis, alerting, and measurement across the system. Ensure downstream performance, reliability, and security work has trustworthy telemetry.
22
23## Inputs Required
24
25- Architecture diagrams and component inventory.
26- Existing logging/monitoring/tracing configuration (if any).
27- Current incidents, outages, or blind spots experienced by the team.
28- SLAs/SLOs, business KPIs, or compliance reporting requirements.
29
30## Outputs
31
32- **Observability plan** detailing metrics, logs, traces, dashboards, and retention policies.
33- **Instrumentation backlog** with implementation tasks, owners, and acceptance criteria.
34- **SLO dashboard specification** covering golden signals, alert thresholds, and runbook links.
35- Updated runbook or escalation paths if gaps were discovered.
36
37## Process
38
391. Audit current telemetry coverage, tooling, and data retention. Document gaps.
402. Define observability objectives aligned with user journeys and business KPIs.
413. Design instrumentation strategy: metrics taxonomy, structured logging, trace spans, event schemas.
424. Establish SLOs, SLIs, and alerting strategy with on-call expectations and noise controls.
435. Produce dashboards/reporting requirements and data governance notes.
446. Create backlog with prioritized instrumentation tasks and verification approach.
45
46## Quality Gates
47
48- Every critical user journey has metrics and alerts defined (latency, errors, saturation, traffic).
49- Logging standards specify structure, PII handling, and retention.
50- Alert runbooks documented or flagged for creation.
51- Observability plan references integration with performance, security, and incident workflows.
52
53## Error Handling
54
55- If telemetry tooling is undecided, present comparative options with trade-offs.
56- Highlight dependencies on platform teams or infrastructure before finalizing timeline.
57- Escalate when observability requirements conflict with compliance or privacy constraints.
majiayu000