fta-code-level

Generate a fault tree analysis by inputting a target method; the skill isolates its signature and dependencies, decomposes control flow and exception surface into OR/AND gates, and outputs a Mermaid diagram with a Markdown traceability table.

Code-level fault tree analysis decomposes functions into deterministic fault trees, connecting logical gates to concrete exceptions and invalid states. You need it when mapping testable resilience artifacts for critical methods to identify failures and mitigations.

Yes, the skill maps try/catch blocks to OR/AND gates automatically by decomposing the target method's flow, capturing each leaf as a concrete exception or invalid state, and annotating mitigations where present.

Create a Mermaid diagram for exceptions by running the skill on a target method. It produces a deterministic Mermaid diagram mapping logical gates to concrete exceptions and invalid states, alongside a Markdown traceability table.

Yes, fault tree analysis identifies where to add guards, fallbacks, and retries by mapping each leaf to its remediation snippet. The generated Markdown traceability table provides guidance for improving resilience in critical methods.

Mapping code-level fault trees using Mermaid diagrams is limited to the target method's isolated signature and dependencies. It focuses on deterministic control flow and exception surface mapping, producing static artifacts rather than dynamic runtime resilience analysis.