Skip to content
Back to skills

Mitigation Validation

ASecurity

Tactic: Run mini-FMEA on proposed mitigations to verify they do not introduce new failure modes. Prevents mitigation-induced risks.

  • 417 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
researchdocumentation

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill mitigation-validation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mitigation Validation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mitigation Validation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-mitigation-validation/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-mitigation-validation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mitigation-validation
description: "Tactic: Run mini-FMEA on proposed mitigations to verify they do not introduce new failure modes. Prevents mitigation-induced risks."
type: tactic
used-by: [failure-anticipation]
strategies: [design-fmea, process-fmea, mitigation-design]
---

# Mitigation Validation Tactic

Validate that proposed mitigations do not introduce new failure modes — a mini-FMEA on the mitigations themselves.

## Orchestration

1. Receive proposed mitigation measures from mitigation-design-sop
2. **failure-mode-extraction** identifies potential failure modes of each mitigation:
   - Could the prevention measure fail?
   - Could the detection mechanism produce false negatives?
   - Could the response plan create new problems?
3. **severity-scoring** rates new failure modes
4. If any new mode scores H-priority:
   - Flag mitigation as risky
   - **mitigation-design-sop** redesigns or adds safeguards
   - Re-validate (max 2 iterations to prevent infinite loops)
5. **re-scoring** confirms final S/O/D with validated mitigations

## Iteration Control

- Max validation iterations: 2 (prevent infinite recursion)
- If still H-priority after 2 iterations: escalate to human review
- Document residual risk for accepted mitigations

## Subagents Dispatched

- failure-mode-extraction (mitigation failure identification)
- severity-scoring (new risk assessment)
- mitigation-design-sop (redesign if needed)
- re-scoring (final confirmation)

## Termination Conditions

- All mitigations validated as not introducing H-priority risks
- Max iterations reached (escalate with documentation)
- Residual risk accepted and documented

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…