Tactic: Trace upstream causes and downstream effects of each failure mode. Builds multi-level cause-mode-effect chains for systemic understanding.
Scanned 6/1/2026
Install to Claude Code
npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill failure-chain-tracing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Failure Chain Tracing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/yogsoth-ai-failure-chain-tracing)More formats (shields.io, HTML) on the badges page.
---
name: failure-chain-tracing
description: "Tactic: Trace upstream causes and downstream effects of each failure mode. Builds multi-level cause-mode-effect chains for systemic understanding."
type: tactic
used-by: [failure-anticipation]
strategies: [prospective-hindsight, design-fmea, process-fmea]
---
# Failure Chain Tracing Tactic
Trace each failure mode both upstream (root causes) and downstream (cascading effects) to build complete causal chains.
## Orchestration
1. Start from identified failure mode
2. **failure-chain-construction** traces upstream:
- Why could this mode occur? (immediate cause)
- Why could that cause occur? (root cause)
- Repeat to budget depth (2/4/6 levels)
3. **failure-chain-construction** traces downstream:
- What effect does this mode produce? (local effect)
- What does that effect cause? (system-level effect)
- What is the end impact? (customer/stakeholder effect)
4. Chain validated for logical consistency
5. Shared causes across multiple modes flagged as systemic risks
## Depth Control
- Budget S: 2 levels (immediate cause → mode → local effect)
- Budget M: 4 levels (root cause → ... → system effect)
- Budget L: 6 levels (full chain with environmental factors)
## Subagents Dispatched
- failure-chain-construction (upstream and downstream tracing)
- severity-scoring (end-effect severity assessment)
## Termination Conditions
- Chain depth exhausted per budget
- Root cause reached (no further upstream cause identifiable)
- End effect reached (stakeholder-level impact identified)
- Circular dependency detected (flag and stop)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!