reliability-engineering

Defining SLIs and SLOs is accomplished by applying a neutral reliability model to produce evidence-based service quality indicators and miss-policies. The Skill generates these targets using a private model checkout or bundled references when private content is unavailable.

Structuring incident aftercare and postmortems involves documenting contributing causes and concrete action items to close operational feedback loops. This Skill rationalizes postmortem learning by applying neutral reliability models to coordinate incident response and track improvements.

Creating a resilience plan requires designing resilience experiments and miss-policy guidance to direct failure handling and recovery activities. This Skill generates operational readiness plans using a neutral reliability model to coordinate service reliability work.

Yes, you can use a private reliability model checkout to generate service indicators, miss-policies, and resilience plans. When a private model is unavailable, the Skill automatically falls back to bundled references to rationalize reliability work.

Miss-policy generation works by producing neutral models that define how services handle SLO misses and failure recovery. The Skill applies deterministic sre-rules to rationalize miss-policies and delegates provider-specific outputs to observability-engineering.

You should delegate provider-specific artifacts to observability-engineering when deterministic sre-rules generation requests provider-specific outputs. This Skill handles the core reliability modeling, SLIs, and SLOs, while delegating specialized observability outputs to that component.