maintenance-philosophy

Map software subsystem failure modes to reactive, preventive, predictive, reliability-centered, or design-out maintenance strategies.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill maintenance-philosophy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintenance-philosophy
Source: https://github.com/NlightNFotis/skills/tree/main/maintenance-philosophy
Command: npx skills add https://github.com/NlightNFotis/skills --skill maintenance-philosophy

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about maintenance-philosophy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right maintenance strategy for my software subsystems?

Choosing a maintenance strategy requires decomposing systems into subsystems, analyzing failure modes, and scoring criticality to map each component to reactive, preventive, predictive, RCM, or design-out postures. This approach aligns maintenance actions with monitoring triggers.

What is reliability-centered maintenance and when should I apply it to software?

Reliability-centered maintenance (RCM) is a strategy that prioritizes maintenance actions based on failure behavior and system criticality. Apply RCM to software subsystems when failure modes require explicit postures that reduce on-call load and align monitoring with actionable alerts.

How do I reduce on-call overload by aligning monitoring with maintenance actions?

Reduce on-call overload by mapping failure modes to specific maintenance postures and retiring monitoring metrics that do not drive action. This explicit alignment ensures alerts correspond to reactive, preventive, or predictive maintenance triggers for each subsystem.

Can I use failure mode analysis to plan tech debt and dependency lifecycle reviews?

Yes, failure mode analysis breaks systems into subsystems to create a maintenance ledger for tech debt planning and dependency lifecycle reviews. Scoring criticality and assessing bathtub-curve lifecycle phases determines whether to upgrade, monitor, or design-out components.

What is the best way to decide when to leave stable systems alone instead of upgrading?

The best way to decide if stable systems need no upgrades is assessing MTBF, MTTR, and bathtub-curve lifecycle phase. Systems in stable lifecycle phases with low criticality scores can safely remain in a reactive maintenance posture without blanket preventive upgrades.

How does bathtub-curve lifecycle assessment factor into preventive maintenance planning?

Bathtub-curve lifecycle assessment maps subsystem failure rates over time to determine if preventive maintenance is needed. It identifies wear-out phases where preventive or predictive postures reduce failures, and stable phases where reactive maintenance is sufficient.