Generate machine-readable FMEDA artifacts computing SPFM, LFM, and PMHF metrics.
npx skills add https://github.com/robotijn/ctoc --skill fmeda-analyzer
Please help me install this Agent Skill. Skill: fmeda-analyzer Source: https://github.com/robotijn/ctoc/tree/main/skills/safety/fmeda-analyzer Command: npx skills add https://github.com/robotijn/ctoc --skill fmeda-analyzer
This Skill solves the critical need for structured, quantifiable Failure Modes Effects and Diagnostic Analysis (FMEDA) required for functional safety certification of safety-critical hardware and software systems. Without a rigorous FMEDA, teams cannot verify compliance with ISO 26262, IEC 61508, and related regulatory standards, leading to rejected safety cases, costly redesigns, or unsafe products reaching market.
Use the fmeda-analyzer skill to generate a complete, compliant FMEDA artifact for your ASIL-D brake pressure monitoring system, including all component failure modes, diagnostic coverage calculations, and regulatory metric verification.
High-intent search queries and answers about installing and using this skill.
Generate a compliant FMEDA for ISO 26262 by enumerating credible component failure modes, classifying their safety impact, and computing Single-Point Fault Metric (SPFM) values to verify ASIL D regulatory compliance. This produces an audit-ready artifact.
A Failure Modes Effects and Diagnostic Analysis (FMEDA) for functional safety is a structured analysis that systematically lists all credible failure modes for digital ICs and software units, classifying each as safe, dangerous detected, or latent to quantify safety impact for certification.
Calculate Single-Point Fault Metric (SPFM) and Latent Fault Metric (LFM) for IEC 61508 SIL 3 systems by analyzing diagnostic coverage for each dangerous failure mode and computing the ratios against total failure rates to verify they meet regulatory thresholds.
Yes, you can use FMEDA analysis for medical device IEC 62304 Class C software units. The analysis applies to safety-critical software development by enumerating credible software failure modes and classifying their safety impact for regulatory certification.
Flag undiagnosed dangerous failure modes in an automotive FMEDA artifact by systematically classifying each mode's diagnostic coverage and generating alerts for critical gaps, including unsourced failure rates and unanalyzed common-cause failures before safety case submission.
pangonIdentify software components from design artifacts and create code phase directories.
ffffffffelixDraft and review ISO 26262 safety work products for automotive E/E systems.
tangyangchao578-artAutomate functional safety analysis and FMEDA design for ISO 26262 compliance.
robotijnRecommend validated redundancy patterns from FMEDA and fault tree data.
