Generate a JSON-formatted FMEA entry from a requirement or architecture element.
npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-fmea
Please help me install this Agent Skill. Skill: pharaoh-fmea Source: https://github.com/useblocks/pharaoh/tree/main/skills/pharaoh-fmea Command: npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-fmea
Automatically derive a single FMEA entry from a given requirement or architecture element and emit a structured JSON artifact for safety analysis, including fields for cause, effect, severity, occurrence, detection, and RPN.
Invoke pharaoh-fmea with a parent_id (and optional failure_mode) to generate a JSON-formatted FMEA entry.
High-intent search queries and answers about installing and using this skill.
To generate an FMEA entry from a requirement, you provide the parent element ID and an optional safety context. The tool resolves the requirement body and outputs a structured JSON object containing the failure mode, cause, effect, severity, occurrence, detection, and RPN.
FMEA failure mode analysis identifies potential ways a system element can fail and assigns risk scores. It calculates a Risk Priority Number (RPN) by evaluating severity, occurrence, and detection metrics, justifying each score using the parent requirement body and provided safety context.
Automating risk analysis for multiple architecture elements requires invoking the tool separately for each element. Each invocation handles exactly one failure mode per parent element, resolving the specific architecture component from needs.json to produce an individual structured JSON artifact.
Yes, a needs.json file is required to perform safety traceability and risk assessment. The tool uses this file to resolve the parent_id, locating the specific requirement or architecture element needed to derive the failure mode and generate the structured JSON output.
To include safety context when calculating RPN, you provide an optional safety_context input alongside the parent_id. The tool applies this context to influence the scoring of severity, occurrence, and detection, using it to justify the generated risk metrics.
The best way to structure FMEA data for downstream risk audits is to emit a ready-to-consume JSON object. This structured format includes failure mode details, RPN scores, mitigations, and justifications, ensuring traceability and seamless integration with risk assessment workflows.
useblocksDraft a single sphinx-needs architecture element with an RST directive block.
Tonybleything76Implement ISO 14971:2019 workflows for medical device risk management.
dtsongEnumerate system component failure modes and design mitigations for resilience.
nroze22Conduct FMEA risk assessments for clinical trial EDC systems.
