What problem does it solve?
This Skill helps you decide how each subsystem should be maintained over time instead of defaulting to reactive firefighting, blanket upgrades, or monitoring everything without a plan.
Core Features & Use Cases
- Maintenance strategy selection: Choose between reactive, preventive, predictive, reliability-centered maintenance, or design-out approaches based on criticality, MTBF, MTTR, detectability, and lifecycle phase.
- Failure-mode-based planning: Break systems into subsystems and failure modes so each one gets an explicit maintenance posture with a clear rationale.
- Monitoring alignment: Identify which alerts and metrics are actually needed for the chosen strategy, and retire monitoring that does not drive action.
- Use cases: Useful for reducing on-call overload, turning tech debt into a maintenance ledger, planning service portfolios with mixed criticality, and deciding when to leave stable systems alone.
Quick Start
Ask the maintenance-philosophy skill to evaluate your service by subsystem and recommend reactive, preventive, predictive, or RCM maintenance with monitoring actions and deferred-maintenance risks.