skills.rest
NlightNFotis
NlightNFotisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

failure-mode-effects-analysis

Analyze components and workflows by scoring failure modes with FMEA.

2|Updated Apr 30, 2026
Search Tags:#system design#reliability#failure modes#risk analysis#fmea#operational readiness#incident prevention
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill failure-mode-effects-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: failure-mode-effects-analysis
Source: https://github.com/NlightNFotis/skills/tree/main/failure-mode-effects-analysis
Command: npx skills add https://github.com/NlightNFotis/skills --skill failure-mode-effects-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you anticipate how a system, workflow, or release could fail before it causes outages, data loss, security exposure, or silent user harm. It turns vague reliability concerns into a structured failure analysis with ranked risks, concrete controls, and assigned actions.

Core Features & Use Cases

  • Structured FMEA workflow: Breaks a component or operation into steps, enumerates failure modes, traces user-visible effects, and scores each risk using severity, occurrence, and detectability.
  • Reliability-focused prioritization: Highlights high-RPN issues, escalates catastrophic failures even when rare, and explicitly calls out single points of failure and common-mode failures.
  • Actionable control planning: Separates prevention, detection, mitigation, and recovery so teams can design balanced safeguards instead of relying on cleanup after incidents.
  • Use cases: Ideal before risky releases, schema migrations, auth changes, data backfills, new critical dependencies, and irreversible automation such as deletes, payments, or outbound sends.

Quick Start

Ask the failure-mode-effects-analysis skill to evaluate an upcoming migration or critical workflow and produce a ranked FMEA table with controls, SPOFs, and concrete mitigation actions.

Frequently Asked Questions about failure-mode-effects-analysis

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

FAQPage Schema
How do I run a failure mode analysis before a risky schema migration or data backfill?▼

Failure mode analysis decomposes schema migrations and data backfills into discrete steps, enumerates potential failure modes, traces user-visible effects, and scores reliability risks using severity, occurrence, and detectability metrics.

What is the best way to prioritize reliability risks and identify single points of failure before a deployment?▼

Prioritizing reliability risks involves calculating Risk Priority Numbers (RPN) for each failure mode, explicitly identifying single points of failure (SPOFs), and escalating catastrophic failures even when their occurrence probability is rare.

When do I need to perform FMEA scoring for operational workflows and irreversible automation?▼

FMEA scoring is needed before executing irreversible automation like deletes, payments, or outbound sends, as well as before risky releases, authentication changes, and adding critical dependencies to operational workflows.

How does FMEA help design balanced safeguards for incident prevention instead of relying on post-incident cleanup?▼

FMEA separates controls into prevention, detection, mitigation, and recovery actions, enabling teams to design balanced safeguards that address common-mode failures and reduce reliance on cleanup after incidents occur.

Can I use failure mode effects analysis for rollback planning and critical dependency evaluation?▼

Yes, failure mode effects analysis applies directly to rollback planning and critical dependency evaluation by tracing the effects of component failures and ranking reliability risks to ensure operational readiness.

What are the limitations of using FMEA for system design and risk analysis?▼

FMEA requires stepwise decomposition of components and workflows, meaning it is only as thorough as the operational steps defined; it cannot predict failure modes for system interactions that are not explicitly enumerated during the analysis.

Related Skills

Explore More Software Engineering Skills→
MicrockMicrock
322

simpy

Model discrete-event systems with SimPy processes and shared resources.

Community
Intermediate
satsilemsatsilem
4

seneca

Identify failure modes and prepare contingency plans for high-stakes decisions.

Community
Advanced
radenadriradenadri

observability-audit

Audit observability data to identify gaps in logging, monitoring, tracing, and alerting.

Community
Advanced
chendongqichendongqi
110

quality-quality-risk-manager

Identify and manage quality risks with FMEA scoring and risk registers.

Community
Advanced