What problem does it solve? Choosing and documenting an observability strategy (monitoring platform, logging, tracing, alerting) is often ad-hoc and undocumented. This Skill guides a structured assessment, writes the decision into the project's adoption files, and records it as a decision log so the rationale stays consistent and traceable. ## Core Features & Use Cases - Resolution Cascade: Resolves the decision via argument override, existing adoption confirmation, or a full assessment, making repeated runs idempotent. - Guideline-Driven Evaluation: Reads observability guidelines (tool comparisons, decision trees, structured logging, metrics, alerting) plus project context like the PRD to recommend a platform such as Grafana, Datadog, or Prometheus. - Adoption & Decision Recording: Writes only the observability section of infrastructure.md (preserving other sections) and composes /capability-record-decision to create an ADR or ADL. - Use Case: During project bootstrap, run the assessment to pick a monitoring stack, document it in adoption/tech/infrastructure.md, and backfill a decision record if one is missing. ## Quick Start Ask the AI to assess the observability strategy for this project and record the chosen platform, logging, tracing, and alerting approach in infrastructure.md.
