observation-minimum-set

Observability gaps occur when diagnostic signals fail to expose failures. This Skill delivers a minimal set of practices—assumption logs, type checking, boundary tests, security scanning, and operational monitoring—that cover six failure modes: spec violations, build errors, boundary failures, dependency vulnerabilities, concurrency issues, and operational faults. Compare your current coverage against these six categories to prioritize improvements.

A minimal set spans executable specifications with assumption logs, clean builds with type checking and linting, boundary and property tests, supply-chain hardening via lockfiles and vulnerability scans, and operational observability through startup validation, health checks, structured logs with correlation IDs, and metrics. This combination cost-effectively sustains quality across spec, dependency, security, and operational failure modes.

Pre-release checks confirm signal exposure and reproducibility by validating assumption logs, type safety, test boundaries, secret and vulnerability scans, and operational checks. This Skill provides checklists and templates for gap analysis so you can measure coverage against six failure modes and roadmap incremental augmentations before deployment.

Yes. This Skill supports ongoing verification and quality-improvement retrospectives by exposing which failure modes lack adequate signals in your current environment. Templates and reports help teams review coverage gaps and plan targeted enhancements across spec, build, test, security, concurrency, and operational domains.

The minimal set is designed for cost-effectiveness across project scales. It enforces independence—each practice stands alone—so you can adopt incrementally. Concurrency observability is optional, letting teams scale coverage to their context without mandatory overhead.

Ad-hoc observability creates blind spots; this approach enforces executable specification, systematic coverage across six failure modes, and reproducibility through checklists and templates. It delivers predictable signal exposure for spec violations, build errors, boundary failures, dependency risks, concurrency issues, and operational faults in every environment.